Apparatus for transmitting broadcast signals, apparatus for receiving broadcast signals, method of transmitting broadcast signals and method of receiving broadcast signals

ABSTRACT

The present invention is related to a method of processing a broadcast service in an apparatus. The method may comprise: receiving a broadcast signal; receiving, from an application running on the apparatus, a request based on a first Application Programming Interface (API); generating a first JavaScript Object Notation (JSON) object by including the URL for the requested OSN; and delivering, to the application, the first JSON object in response to the first API.

This application claims the benefit of U.S. Provisional PatentApplication Nos. 62/519,100, filed on Jun. 13, 2017, 62/519,151, filedon Jun. 13, 2017, and 62/533,674, filed on Jul. 18, 2017, which arehereby incorporated by reference as if fully set forth herein.

BACKGROUND OF THE INVENTION Field of the Invention

The present invention relates to an apparatus for transmitting broadcastsignals, an apparatus for receiving broadcast signals, a method oftransmitting broadcast signals, and a method of receiving broadcastsignals.

Discussion of the Related Art

As analog broadcast signal transmission comes to an end, varioustechnologies for transmitting/receiving digital broadcast signals havebeen developed. A digital broadcast signal may include a larger amountof video/audio data than an analog broadcast signal and further includevarious types of additional data in addition to the video/audio data.

SUMMARY OF THE INVENTION

That is, a digital broadcast system can provide high definition (HD)images, multi-channel audio and various additional services. However,data transmission efficiency for transmission of large amounts of data,robustness of transmission/reception networks and network flexibility inconsideration of mobile reception equipment need to be improved fordigital broadcast.

According to an object of the present invention, as included herein andbriefly described, the present invention proposes a system foreffectively supporting a next-generation broadcast service in anenvironment that supports next-generation hybrid broadcast using aterrestrial broadcast network and an Internet protocol (IP) network, anda related signaling scheme.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the invention and are incorporated in and constitute apart of this application, illustrate embodiment(s) of the invention andtogether with the description serve to explain the principle of theinvention. In the drawings:

FIG. 1 is a diagram showing a protocol stack according to an embodimentof the present invention.

FIG. 2 is a diagram showing a service discovery procedure according toone embodiment of the present invention.

FIG. 3 is a diagram showing a low level signaling (LLS) table and aservice list table (SLT) according to one embodiment of the presentinvention.

FIG. 4 is a diagram showing a USBD and an S-TSID delivered through ROUTEaccording to one embodiment of the present invention.

FIG. 5 is a diagram showing a USBD delivered through MMT according toone embodiment of the present invention.

FIG. 6 is a diagram showing link layer operation according to oneembodiment of the present invention.

FIG. 7 is a diagram showing a link mapping table (LMT) according to oneembodiment of the present invention.

FIG. 8 illustrates a configuration of a broadcast signal transmissionapparatus for future broadcast services according to an embodiment ofthe present invention.

FIG. 9 illustrates a write operation of a time interleaver according toan embodiment of the present invention.

FIG. 10 illustrates an interleaving address generator including a mainpseudo-random binary sequence (PRBS) generator and a sub-PRBS generatoraccording to each FFT mode which are included in a frequency interleaveraccording to an embodiment of the present invention.

FIG. 11 is a diagram of an apparatus for processing a broadcast serviceaccording to an aspect of the present invention.

FIG. 12 is a diagram a URL request API according to an embodiment of thepresent invention.

FIG. 13 is a diagram showing an application example of a URL request APIaccording to the present invention.

FIG. 14 is a diagram showing a signaling change notification APIaccording to an embodiment of the present invention.

FIG. 15 is a diagram showing an application example of a signalingchange notification API according to the present invention.

FIG. 16 is a diagram showing an example of a signaling change subscribeAPI according to an embodiment of the present invention

FIG. 17 is a diagram showing a signaling change unsubscribe APIaccording to an embodiment of the present invention.

FIG. 18 is a diagram showing an OSN request API according to anembodiment of the present invention.

FIG. 19 is a diagram showing an OSN notification API according to anembodiment of the present invention.

FIG. 20 is a diagram showing a screen clean request API according to anembodiment of the present invention.

FIG. 21 is a diagram showing a screen clean notification API accordingto an embodiment of the present invention.

FIG. 22 is a diagram showing a display override request API according toan embodiment of the present invention.

FIG. 23 is a diagram showing a method of acquiring a WebSocket severaddress by an application according to an embodiment of the presentinvention.

FIG. 24 is a diagram showing a method of processing a broadcast serviceto be performed by a broadcast service processing apparatus according toan embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

Reference will now be made in detail to the preferred embodiments of thepresent invention, examples of which are illustrated in the accompanyingdrawings. The detailed description, which will be given below withreference to the accompanying drawings, is intended to explain exemplaryembodiments of the present invention, rather than to show the onlyembodiments that may be implemented according to the present invention.The following detailed description includes specific details in order toprovide a thorough understanding of the present invention. However, itwill be apparent to those skilled in the art that the present inventionmay be practiced without such specific details.

Although most terms used in the present invention have been selectedfrom general ones widely used in the art, some terms have beenarbitrarily selected by the applicant and their meanings are explainedin detail in the following description as needed. Thus, the presentinvention should be understood based upon the intended meanings of theterms rather than their simple names or meanings.

The present invention provides apparatuses and methods for transmittingand receiving broadcast signals for future broadcast services. Futurebroadcast services according to an embodiment of the present inventioninclude a terrestrial broadcast service, a mobile broadcast service, aUHDTV service, etc. The present invention may process broadcast signalsfor the future broadcast services through non-MIMO or MIMO according toone embodiment. A non-MIMO scheme according to an embodiment of thepresent invention may include a multiple input single output (MISO)scheme, a single input single output (SISO) scheme, etc. The presentinvention proposes a physical profile (or system) optimized to minimizereceiver complexity while attaining the performance required for aparticular use case.

FIG. 1 is a diagram showing a protocol stack according to an embodimentof the present invention.

A service may be delivered to a receiver through a plurality of layers.First, a transmission side may generate service data. The service datamay be processed for transmission at a delivery layer of thetransmission side and the service data may be encoded into a broadcastsignal and transmitted over a broadcast or broadband network at aphysical layer.

Here, the service data may be generated in an ISO base media file format(BMFF). ISO BMFF media files may be used for broadcast/broadband networkdelivery, media encapsulation and/or synchronization format. Here, theservice data is all data related to the service and may include servicecomponents configuring a linear service, signaling information thereof,non real time (NRT) data and other files.

The delivery layer will be described. The delivery layer may provide afunction for transmitting service data. The service data may bedelivered over a broadcast and/or broadband network.

Broadcast service delivery may include two methods.

As a first method, service data may be processed in media processingunits (MPUs) based on MPEG media transport (MMT) and transmitted usingan MMT protocol (MMTP). In this case, the service data delivered usingthe MMTP may include service components for a linear service and/orservice signaling information thereof.

As a second method, service data may be processed into DASH segments andtransmitted using real time object delivery over unidirectionaltransport (ROUTE), based on MPEG DASH. In this case, the service datadelivered through the ROUTE protocol may include service components fora linear service, service signaling information thereof and/or NRT data.That is, the NRT data and non-timed data such as files may be deliveredthrough ROUTE.

Data processed according to MMTP or ROUTE protocol may be processed intoIP packets through a UDP/IP layer. In service data delivery over thebroadcast network, a service list table (SLT) may also be delivered overthe broadcast network through a UDP/IP layer. The SLT may be deliveredin a low level signaling (LLS) table. The SLT and LLS table will bedescribed later.

IP packets may be processed into link layer packets in a link layer. Thelink layer may encapsulate various formats of data delivered from ahigher layer into link layer packets and then deliver the packets to aphysical layer. The link layer will be described later.

In hybrid service delivery, at least one service element may bedelivered through a broadband path. In hybrid service delivery, datadelivered over broadband may include service components of a DASHformat, service signaling information thereof and/or NRT data. This datamay be processed through HTTP/TCP/IP and delivered to a physical layerfor broadband transmission through a link layer for broadbandtransmission.

The physical layer may process the data received from the delivery layer(higher layer and/or link layer) and transmit the data over thebroadcast or broadband network. A detailed description of the physicallayer will be given later.

The service will be described. The service may be a collection ofservice components displayed to a user, the components may be of variousmedia types, the service may be continuous or intermittent, the servicemay be real time or non real time, and a real-time service may include asequence of TV programs.

The service may have various types. First, the service may be a linearaudio/video or audio service having app based enhancement. Second, theservice may be an app based service, reproduction/configuration of whichis controlled by a downloaded application. Third, the service may be anESG service for providing an electronic service guide (ESG). Fourth, theservice may be an emergency alert (EA) service for providing emergencyalert information.

When a linear service without app based enhancement is delivered overthe broadcast network, the service component may be delivered by (1) oneor more ROUTE sessions or (2) one or more MMTP sessions.

When a linear service having app based enhancement is delivered over thebroadcast network, the service component may be delivered by (1) one ormore ROUTE sessions or (2) zero or more MMTP sessions. In this case,data used for app based enhancement may be delivered through a ROUTEsession in the form of NRT data or other files. In one embodiment of thepresent invention, simultaneous delivery of linear service components(streaming media components) of one service using two protocols may notbe allowed.

When an app based service is delivered over the broadcast network, theservice component may be delivered by one or more ROUTE sessions. Inthis case, the service data used for the app based service may bedelivered through the ROUTE session in the form of NRT data or otherfiles.

Some service components of such a service, some NRT data, files, etc.may be delivered through broadband (hybrid service delivery).

That is, in one embodiment of the present invention, linear servicecomponents of one service may be delivered through the MMT protocol. Inanother embodiment of the present invention, the linear servicecomponents of one service may be delivered through the ROUTE protocol.In another embodiment of the present invention, the linear servicecomponents of one service and NRT data (NRT service components) may bedelivered through the ROUTE protocol. In another embodiment of thepresent invention, the linear service components of one service may bedelivered through the MMT protocol and the NRT data (NRT servicecomponents) may be delivered through the ROUTE protocol. In theabove-described embodiments, some service components of the service orsome NRT data may be delivered through broadband. Here, the app basedservice and data regarding app based enhancement may be delivered overthe broadcast network according to ROUTE or through broadband in theform of NRT data. NRT data may be referred to as locally cached data.

Each ROUTE session includes one or more LCT sessions for wholly orpartially delivering content components configuring the service. Instreaming service delivery, the LCT session may deliver individualcomponents of a user service, such as audio, video or closed captionstream. The streaming media is formatted into a DASH segment.

Each MMTP session includes one or more MMTP packet flows for deliveringall or some of content components or an MMT signaling message. The MMTPpacket flow may deliver a component formatted into MPU or an MMTsignaling message.

For delivery of an NRT user service or system metadata, the LCT sessiondelivers a file based content item. Such content files may includeconsecutive (timed) or discrete (non-timed) media components of the NRTservice or metadata such as service signaling or ESG fragments. Systemmetadata such as service signaling or ESG fragments may be deliveredthrough the signaling message mode of the MMTP.

A receiver may detect a broadcast signal while a tuner tunes tofrequencies. The receiver may extract and send an SLT to a processingmodule. The SLT parser may parse the SLT and acquire and store data in achannel map. The receiver may acquire and deliver bootstrap informationof the SLT to a ROUTE or MMT client. The receiver may acquire and storean SLS. USBD may be acquired and parsed by a signaling parser.

FIG. 2 is a diagram showing a service discovery procedure according toone embodiment of the present invention.

A broadcast stream delivered by a broadcast signal frame of a physicallayer may carry low level signaling (LLS). LLS data may be carriedthrough payload of IP packets delivered to a well-known IP address/port.This LLS may include an SLT according to type thereof. The LLS data maybe formatted in the form of an LLS table. A first byte of every UDP/IPpacket carrying the LLS data may be the start of the LLS table. Unlikethe shown embodiment, an IP stream for delivering the LLS data may bedelivered to a PLP along with other service data.

The SLT may enable the receiver to generate a service list through fastchannel scan and provides access information for locating the SLS. TheSLT includes bootstrap information. This bootstrap information mayenable the receiver to acquire service layer signaling (SLS) of eachservice. When the SLS, that is, service signaling information, isdelivered through ROUTE, the bootstrap information may include an LCTchannel carrying the SLS, a destination IP address of a ROUTE sessionincluding the LCT channel and destination port information. When the SLSis delivered through the MMT, the bootstrap information may include adestination IP address of an MMTP session carrying the SLS anddestination port information.

In the shown embodiment, the SLS of service #1 described in the SLT isdelivered through ROUTE and the SLT may include bootstrap informationsIP1, dIP1 and dPort1 of the ROUTE session including the LCT channeldelivered by the SLS. The SLS of service #2 described in the SLT isdelivered through MMT and the SLT may include bootstrap informationsIP2, dIP2 and dPort2 of the MMTP session including the MMTP packet flowdelivered by the SLS.

The SLS is signaling information describing the properties of theservice and may include receiver capability information forsignificantly reproducing the service or providing information foracquiring the service and the service component of the service. Wheneach service has separate service signaling, the receiver acquiresappropriate SLS for a desired service without parsing all SLSs deliveredwithin a broadcast stream.

When the SLS is delivered through the ROUTE protocol, the SLS may bedelivered through a dedicated LCT channel of a ROUTE session indicatedby the SLT. In some embodiments, this LCT channel may be an LCT channelidentified by tsi=0. In this case, the SLS may include a user servicebundle description (USBD)/user service description (USD), service-basedtransport session instance description (S-TSID) and/or mediapresentation description (MPD).

Here, USBD/USD is one of SLS fragments and may serve as a signaling hubdescribing detailed description information of a service. The USBD mayinclude service identification information, device capabilityinformation, etc. The USBD may include reference information (URIreference) of other SLS fragments (S-TSID, MPD, etc.). That is, theUSBD/USD may reference the S-TSID and the MPD. In addition, the USBD mayfurther include metadata information for enabling the receiver to decidea transmission mode (broadcast/broadband network). A detaileddescription of the USBD/USD will be given below.

The S-TSID is one of SLS fragments and may provide overall sessiondescription information of a transport session carrying the servicecomponent of the service. The S-TSID may provide the ROUTE sessionthrough which the service component of the service is delivered and/ortransport session description information for the LCT channel of theROUTE session. The S-TSID may provide component acquisition informationof service components associated with one service. The S-TSID mayprovide mapping between DASH representation of the MPD and the tsi ofthe service component. The component acquisition information of theS-TSID may be provided in the form of the identifier of the associatedDASH representation and tsi and may or may not include a PLP ID in someembodiments. Through the component acquisition information, the receivermay collect audio/video components of one service and perform bufferingand decoding of DASH media segments. The S-TSID may be referenced by theUSBD as described above. A detailed description of the S-TSID will begiven below.

The MPD is one of SLS fragments and may provide a description of DASHmedia presentation of the service. The MPD may provide a resourceidentifier of media segments and provide context information within themedia presentation of the identified resources. The MPD may describeDASH representation (service component) delivered over the broadcastnetwork and describe additional DASH presentation delivered overbroadband (hybrid delivery). The MPD may be referenced by the USBD asdescribed above.

When the SLS is delivered through the MMT protocol, the SLS may bedelivered through a dedicated MMTP packet flow of the MMTP sessionindicated by the SLT. In some embodiments, the packet_id of the MMTPpackets delivering the SLS may have a value of 00. In this case, the SLSmay include a USBD/USD and/or MMT packet (MP) table.

Here, the USBD is one of SLS fragments and may describe detaileddescription information of a service as in ROUTE. This USBD may includereference information (URI information) of other SLS fragments. The USBDof the MMT may reference an MP table of MMT signaling. In someembodiments, the USBD of the MMT may include reference information ofthe S-TSID and/or the MPD. Here, the S-TSID is for NRT data deliveredthrough the ROUTE protocol. Even when a linear service component isdelivered through the MMT protocol, NRT data may be delivered via theROUTE protocol. The MPD is for a service component delivered overbroadband in hybrid service delivery. The detailed description of theUSBD of the MMT will be given below.

The MP table is a signaling message of the MMT for MPU components andmay provide overall session description information of an MMTP sessioncarrying the service component of the service. In addition, the MP tablemay include a description of an asset delivered through the MMTPsession. The MP table is streaming signaling information for MPUcomponents and may provide a list of assets corresponding to one serviceand location information (component acquisition information) of thesecomponents. The detailed description of the MP table may be defined inthe MMT or modified. Here, the asset is a multimedia data entity, iscombined by one unique ID, and may mean a data entity used to onemultimedia presentation. The asset may correspond to service componentsconfiguring one service. A streaming service component (MPU)corresponding to a desired service may be accessed using the MP table.The MP table may be referenced by the USBD as described above.

The other MMT signaling messages may be defined. Additional informationassociated with the service and the MMTP session may be described bysuch MMT signaling messages.

The ROUTE session is identified by a source IP address, a destination IPaddress and a destination port number. The LCT session is identified bya unique transport session identifier (TSI) within the range of a parentROUTE session. The MMTP session is identified by a destination IPaddress and a destination port number. The MMTP packet flow isidentified by a unique packet_id within the range of a parent MMTPsession.

In case of ROUTE, the S-TSID, the USBD/USD, the MPD or the LCT sessiondelivering the same may be referred to as a service signaling channel.In case of MMTP, the USBD/UD, the MMT signaling message or the packetflow delivering the same may be referred to as a service signalingchannel.

Unlike the shown embodiment, one ROUTE or MMTP session may be deliveredover a plurality of PLPs. That is, one service may be delivered throughone or more PLPs. Unlike the shown embodiment, in some embodiments,components configuring one service may be delivered through differentROUTE sessions. In addition, in some embodiments, components configuringone service may be delivered through different MMTP sessions. In someembodiments, components configuring one service may be divided anddelivered in a ROUTE session and an MMTP session. Although not shown,components configuring one service may be delivered through broadband(hybrid delivery).

FIG. 3 is a diagram showing a low level signaling (LLS) table and aservice list table (SLT) according to one embodiment of the presentinvention.

One embodiment t3010 of the LLS table may include information accordingto an LLS_table_id field, a provider_id field, an LLS_table_versionfield and/or an LLS_table_id field.

The LLS_table_id field may identify the type of the LLS table, and theprovider_id field may identify a service provider associated withservices signaled by the LLS table. Here, the service provider is abroadcaster using all or some of the broadcast streams and theprovider_id field may identify one of a plurality of broadcasters whichis using the broadcast streams. The LLS_table_version field may providethe version information of the LLS table.

According to the value of the LLS_table_id field, the LLS table mayinclude one of the above-described SLT, a rating region table (RRT)including information on a content advisory rating, SystemTimeinformation for providing information associated with a system time, acommon alert protocol (CAP) message for providing information associatedwith emergency alert. In some embodiments, the other information may beincluded in the LLS table.

One embodiment t3020 of the shown SLT may include an @bsid attribute, an@sltCapabilities attribute, an sltInetUrl element and/or a Serviceelement. Each field may be omitted according to the value of the shownUse column or a plurality of fields may be present.

The @bsid attribute may be the identifier of a broadcast stream. The@sltCapabilities attribute may provide capability information requiredto decode and significantly reproduce all services described in the SLT.The sltInetUrl element may provide base URL information used to obtainservice signaling information and ESG for the services of the SLT overbroadband. The sltInetUrl element may further include an @urlTypeattribute, which may indicate the type of data capable of being obtainedthrough the URL.

The Service element may include information on services described in theSLT, and the Service element of each service may be present. The Serviceelement may include an @serviceId attribute, an @sltSvcSeqNum attribute,an @protected attribute, an @majorChannelNo attribute, an@minorChannelNo attribute, an @serviceCategory attribute, an@shortServiceName attribute, an @hidden attribute, an@broadbandAccessRequired attribute, an @svcCapabilities attribute, aBroadcastSvcSignaling element and/or an svcInetUrl element.

The @serviceId attribute is the identifier of the service and the@sltSvcSeqNum attribute may indicate the sequence number of the SLTinformation of the service. The @protected attribute may indicatewhether at least one service component necessary for significantreproduction of the service is protected. The @majorChannelNo attributeand the @minorChannelNo attribute may indicate the major channel numberand minor channel number of the service, respectively.

The @serviceCategory attribute may indicate the category of the service.The category of the service may include a linear A/V service, a linearaudio service, an app based service, an ESG service, an EAS service,etc. The @shortServiceName attribute may provide the short name of theservice. The @hidden attribute may indicate whether the service is fortesting or proprietary use. The @broadbandAccessRequired attribute mayindicate whether broadband access is necessary for significantreproduction of the service. The @svcCapabilities attribute may providecapability information necessary for decoding and significantreproduction of the service.

The BroadcastSvcSignaling element may provide information associatedwith broadcast signaling of the service. This element may provideinformation such as location, protocol and address with respect tosignaling over the broadcast network of the service. Details thereofwill be described below.

The svcInetUrl element may provide URL information for accessing thesignaling information of the service over broadband. The sltInetUrlelement may further include an @urlType attribute, which may indicatethe type of data capable of being obtained through the URL.

The above-described BroadcastSvcSignaling element may include an@slsProtocol attribute, an @slsMajorProtocolVersion attribute, an@slsMinorProtocolVersion attribute, an @slsPlpId attribute, an@slsDestinationIpAddress attribute, an @slsDestinationUdpPort attributeand/or an @slsSourceIpAddress attribute.

The @slsProtocol attribute may indicate the protocol used to deliver theSLS of the service (ROUTE, MMT, etc.). The @slsMajorProtocolVersionattribute and the @slsMinorProtocolVersion attribute may indicate themajor version number and minor version number of the protocol used todeliver the SLS of the service, respectively.

The @slsPlpId attribute may provide a PLP identifier for identifying thePLP delivering the SLS of the service. In some embodiments, this fieldmay be omitted and the PLP information delivered by the SLS may bechecked using a combination of the information of the below-describedLMT and the bootstrap information of the SLT.

The @slsDestinationIpAddress attribute, the @slsDestinationUdpPortattribute and the @slsSourceIpAddress attribute may indicate thedestination IP address, destination UDP port and source IP address ofthe transport packets delivering the SLS of the service, respectively.These may identify the transport session (ROUTE session or MMTP session)delivered by the SLS. These may be included in the bootstrapinformation.

FIG. 4 is a diagram showing a USBD and an S-TSID delivered through ROUTEaccording to one embodiment of the present invention.

One embodiment t4010 of the shown USBD may have a bundleDescription rootelement. The bundleDescription root element may have auserServiceDescription element. The userServiceDescription element maybe an instance of one service.

The userServiceDescription element may include an @globalServiceIDattribute, an @serviceId attribute, an @serviceStatus attribute, an@fullMPDUri attribute, an @sTSIDUri attribute, a name element, aserviceLanguage element, a capabilityCode element and/or adeliveryMethod element. Each field may be omitted according to the valueof the shown Use column or a plurality of fields may be present.

The @globalServiceID attribute is the globally unique identifier of theservice and may be used for link with ESG data(Service@globalServiceID). The @serviceId attribute is a referencecorresponding to the service entry of the SLT and may be equal to theservice ID information of the SLT. The @serviceStatus attribute mayindicate the status of the service. This field may indicate whether theservice is active or inactive.

The @fullMPDUri attribute may reference the MPD fragment of the service.The MPD may provide a reproduction description of a service componentdelivered over the broadcast or broadband network as described above.The @sTSIDUri attribute may reference the S-TSID fragment of theservice. The S-TSID may provide parameters associated with access to thetransport session carrying the service as described above.

The name element may provide the name of the service. This element mayfurther include an @lang attribute and this field may indicate thelanguage of the name provided by the name element. The serviceLanguageelement may indicate available languages of the service. That is, thiselement may arrange the languages capable of being provided by theservice.

The capabilityCode element may indicate capability or capability groupinformation of a receiver necessary to significantly reproduce theservice. This information is compatible with capability informationformat provided in service announcement.

The deliveryMethod element may provide transmission related informationwith respect to content accessed over the broadcast or broadband networkof the service. The deliveryMethod element may include abroadcastAppService element and/or a unicastAppService element. Each ofthese elements may have a basePattern element as a sub element.

The broadcastAppService element may include transmission associatedinformation of the DASH representation delivered over the broadcastnetwork. The DASH representation may include media components over allperiods of the service presentation.

The basePattern element of this element may indicate a character patternused for the receiver to perform matching with the segment URL. This maybe used for a DASH client to request the segments of the representation.Matching may imply delivery of the media segment over the broadcastnetwork.

The unicastAppService element may include transmission relatedinformation of the DASH representation delivered over broadband. TheDASH representation may include media components over all periods of theservice media presentation.

The basePattern element of this element may indicate a character patternused for the receiver to perform matching with the segment URL. This maybe used for a DASH client to request the segments of the representation.Matching may imply delivery of the media segment over broadband.

One embodiment t4020 of the shown S-TSID may have an S-TSID rootelement. The S-TSID root element may include an @serviceId attributeand/or an RS element. Each field may be omitted according to the valueof the shown Use column or a plurality of fields may be present.

The @serviceId attribute is the identifier of the service and mayreference the service of the USBD/USD. The RS element may describeinformation on ROUTE sessions through which the service components ofthe service are delivered. According to the number of ROUTE sessions, aplurality of elements may be present. The RS element may further includean @bsid attribute, an @sIpAddr attribute, an @dIpAddr attribute, an@dport attribute, an @PLPID attribute and/or an LS element.

The @bsid attribute may be the identifier of a broadcast stream in whichthe service components of the service are delivered. If this field isomitted, a default broadcast stream may be a broadcast stream includingthe PLP delivering the SLS of the service. The value of this field maybe equal to that of the @bsid attribute.

The @sIpAddr attribute, the @dIpAddr attribute and the @dport attributemay indicate the source IP address, destination IP address anddestination UDP port of the ROUTE session, respectively. When thesefields are omitted, the default values may be the source address,destination IP address and destination UDP port values of the currentROUTE session delivering the SLS, that is, the S-TSID. This field maynot be omitted in another ROUTE session delivering the servicecomponents of the service, not in the current ROUTE session.

The @PLPID attribute may indicate the PLP ID information of the ROUTEsession. If this field is omitted, the default value may be the PLP IDvalue of the current PLP delivered by the S-TSID. In some embodiments,this field is omitted and the PLP ID information of the ROUTE sessionmay be checked using a combination of the information of thebelow-described LMT and the IP address/UDP port information of the RSelement.

The LS element may describe information on LCT channels through whichthe service components of the service are transmitted. According to thenumber of LCT channel, a plurality of elements may be present. The LSelement may include an @tsi attribute, an @PLPID attribute, an @bwattribute, an @startTime attribute, an @endTime attribute, a SrcFlowelement and/or a RepairFlow element.

The @tsi attribute may indicate the tsi information of the LCT channel.Using this, the LCT channels through which the service components of theservice are delivered may be identified. The @PLPID attribute mayindicate the PLP ID information of the LCT channel. In some embodiments,this field may be omitted. The @bw attribute may indicate the maximumbandwidth of the LCT channel. The @startTime attribute may indicate thestart time of the LCT session and the @endTime attribute may indicatethe end time of the LCT channel.

The SrcFlow element may describe the source flow of ROUTE. The sourceprotocol of ROUTE is used to transmit a delivery object and at least onesource flow may be established within one ROUTE session. The source flowmay deliver associated objects as an object flow.

The RepairFlow element may describe the repair flow of ROUTE. Deliveryobjects delivered according to the source protocol may be protectedaccording to forward error correction (FEC) and the repair protocol maydefine an FEC framework enabling FEC protection.

FIG. 5 is a diagram showing a USBD delivered through MMT according toone embodiment of the present invention.

One embodiment of the shown USBD may have a bundleDescription rootelement. The bundleDescription root element may have auserServiceDescription element. The userServiceDescription element maybe an instance of one service.

The userServiceDescription element may include an @globalServiceIDattribute, an @serviceId attribute, a Name element, a serviceLanguageelement, a contentAdvisoryRating element, a Channel element, ampuComponent element, a routeComponent element, a broadbandComponentelement and/or a ComponentInfo element. Each field may be omittedaccording to the value of the shown Use column or a plurality of fieldsmay be present.

The @globalServiceID attribute, the @serviceId attribute, the Nameelement and/or the serviceLanguage element may be equal to the fields ofthe USBD delivered through ROUTE. The contentAdvisoryRating element mayindicate the content advisory rating of the service. This information iscompatible with content advisory rating information format provided inservice announcement. The Channel element may include informationassociated with the service. A detailed description of this element willbe given below.

The mpuComponent element may provide a description of service componentsdelivered as the MPU of the service. This element may further include an@mmtPackageId attribute and/or an @nextMmtPackageId attribute. The@mmtPackageId attribute may reference the MMT package of the servicecomponents delivered as the MPU of the service. The @nextMmtPackageIdattribute may reference an MMT package to be used after the MMT packagereferenced by the @mmtPackageId attribute in terms of time. Through theinformation of this element, the MP table may be referenced.

The routeComponent element may include a description of the servicecomponents of the service. Even when linear service components aredelivered through the MMT protocol, NRT data may be delivered accordingto the ROUTE protocol as described above. This element may describeinformation on such NRT data. A detailed description of this elementwill be given below.

The broadbandComponent element may include the description of theservice components of the service delivered over broadband. In hybridservice delivery, some service components of one service or other filesmay be delivered over broadband. This element may describe informationon such data. This element may further an @fullMPDUri attribute. Thisattribute may reference the MPD describing the service componentdelivered over broadband. In addition to hybrid service delivery, thebroadcast signal may be weakened due to traveling in a tunnel and thusthis element may be necessary to support handoff between broadband andbroadband. When the broadcast signal is weak, the service component isacquired over broadband and, when the broadcast signal becomes strong,the service component is acquired over the broadcast network to secureservice continuity.

The ComponentInfo element may include information on the servicecomponents of the service. According to the number of service componentsof the service, a plurality of elements may be present. This element maydescribe the type, role, name, identifier or protection of each servicecomponent. Detailed information of this element will be described below.

The above-described Channel element may further include an @serviceGenreattribute, an @serviceIcon attribute and/or a ServiceDescriptionelement. The @serviceGenre attribute may indicate the genre of theservice and the @serviceIcon attribute may include the URL informationof the representative icon of the service. The ServiceDescriptionelement may provide the service description of the service and thiselement may further include an @serviceDescrText attribute and/or an@serviceDescrLang attribute. These attributes may indicate the text ofthe service description and the language used in the text.

The above-described routeComponent element may further include an@sTSIDUri attribute, an @sTSIDDestinationIpAddress attribute, an@sTSIDDestinationUdpPort attribute, an @sTSIDSourceIpAddress attribute,an @sTSIDMajorProtocolVersion attribute and/or an@sTSIDMinorProtocolVersion attribute.

The @sTSIDUri attribute may reference an S-TSID fragment. This field maybe equal to the field of the USBD delivered through ROUTE. This S-TSIDmay provide access related information of the service componentsdelivered through ROUTE. This S-TSID may be present for NRT datadelivered according to the ROUTE protocol in a state of deliveringlinear service component according to the MMT protocol.

The @sTSIDDestinationIpAddress attribute, the @sTSIDDestinationUdpPortattribute and the @sTSIDSourceIpAddress attribute may indicate thedestination IP address, destination UDP port and source IP address ofthe transport packets carrying the above-described S-TSID. That is,these fields may identify the transport session (MMTP session or theROUTE session) carrying the above-described S-TSID.

The @sTSIDMajorProtocolVersion attribute and the@sTSIDMinorProtocolVersion attribute may indicate the major versionnumber and minor version number of the transport protocol used todeliver the above-described S-TSID, respectively.

The above-described ComponentInfo element may further include an@componentType attribute, an @componentRole attribute, an@componentProtectedFlag attribute, an @componentId attribute and/or an@componentName attribute.

The @componentType attribute may indicate the type of the component. Forexample, this attribute may indicate whether the component is an audio,video or closed caption component. The @componentRole attribute mayindicate the role of the component. For example, this attribute mayindicate main audio, music, commentary, etc. if the component is anaudio component. This attribute may indicate primary video if thecomponent is a video component. This attribute may indicate a normalcaption or an easy reader type if the component is a closed captioncomponent.

The @componentProtectedFlag attribute may indicate whether the servicecomponent is protected, for example, encrypted. The @componentIdattribute may indicate the identifier of the service component. Thevalue of this attribute may be the asset_id (asset ID) of the MP tablecorresponding to this service component. The @componentName attributemay indicate the name of the service component.

FIG. 6 is a diagram showing link layer operation according to oneembodiment of the present invention.

The link layer may be a layer between a physical layer and a networklayer. A transmission side may transmit data from the network layer tothe physical layer and a reception side may transmit data from thephysical layer to the network layer (t6010). The purpose of the linklayer is to compress (abstract) all input packet types into one formatfor processing by the physical layer and to secure flexibility andexpandability of an input packet type which is not defined yet. Inaddition, the link layer may provide option for compressing(abstracting) unnecessary information of the header of input packets toefficiently transmit input data. Operation such as overhead reduction,encapsulation, etc. of the link layer is referred to as a link layerprotocol and packets generated using this protocol may be referred to aslink layer packets. The link layer may perform functions such as packetencapsulation, overhead reduction and/or signaling transmission.

At the transmission side, the link layer (ALP) may perform an overheadreduction procedure with respect to input packets and then encapsulatethe input packets into link layer packets. In addition, in someembodiments, the link layer may perform encapsulation into the linklayer packets without performing the overhead reduction procedure. Dueto use of the link layer protocol, data transmission overhead on thephysical layer may be significantly reduced and the link layer protocolaccording to the present invention may provide IP overhead reductionand/or MPEG-2 TS overhead reduction.

When the shown IP packets are input as input packets (t6010), the linklayer may sequentially perform IP header compression, adaptation and/orencapsulation. In some embodiments, some processes may be omitted. Forexample, the RoHC module may perform IP packet header compression toreduce unnecessary overhead. Context information may be extractedthrough the adaptation procedure and transmitted out of band. The IPheader compression and adaption procedure may be collectively referredto as IP header compression. Thereafter, the IP packets may beencapsulated into link layer packets through the encapsulationprocedure.

When MPEG 2 TS packets are input as input packets, the link layer maysequentially perform overhead reduction and/or an encapsulationprocedure with respect to the TS packets. In some embodiments, someprocedures may be omitted. In overhead reduction, the link layer mayprovide sync byte removal, null packet deletion and/or common headerremoval (compression). Through sync byte removal, overhead reduction of1 byte may be provided per TS packet. Null packet deletion may beperformed in a manner in which reinsertion is possible at the receptionside. In addition, deletion (compression) may be performed in a mannerin which common information between consecutive headers may be restoredat the reception side. Some of the overhead reduction procedures may beomitted. Thereafter, through the encapsulation procedure, the TS packetsmay be encapsulated into link layer packets. The link layer packetstructure for encapsulation of the TS packets may be different from thatof the other types of packets.

First, IP header compression will be described.

The IP packets may have a fixed header format but some informationnecessary for a communication environment may be unnecessary for abroadcast environment. The link layer protocol may compress the headerof the IP packet to provide a mechanism for reducing broadcast overhead.

IP header compression may employ a header compressor/decompressor and/oran adaptation module. The IP header compressor (RoHC compressor) mayreduce the size of each IP packet header based on the RoHC scheme.Thereafter, the adaptation module may extract context information andgenerate signaling information from each packet stream. A receiver mayparse signaling information associated with the packet stream and attachcontext information to the packet stream. The RoHC decompressor mayrestore the packet header to reconfigure an original IP packet.Hereinafter, IP header compression may mean only IP header compressionby a header compression or a combination of IP header compression and anadaptation process by an adaptation module. The same is true indecompressing.

Hereinafter, adaptation will be described.

In transmission of a single-direction link, when the receiver does nothave context information, the decompressor cannot restore the receivedpacket header until complete context is received. This may lead tochannel change delay and turn-on delay. Accordingly, through theadaptation function, configuration parameters and context informationbetween the compressor and the decompressor may be transmitted out ofband. The adaptation function may provide construction of link layersignaling using context information and/or configuration parameters. Theadaptation function may use previous configuration parameters and/orcontext information to periodically transmit link layer signalingthrough each physical frame.

Context information is extracted from the compressed IP packets andvarious methods may be used according to adaptation mode.

Mode #1 refers to a mode in which no operation is performed with respectto the compressed packet stream and an adaptation module operates as abuffer.

Mode #2 refers to a mode in which an IR packet is detected from acompressed packet stream to extract context information (static chain).After extraction, the IR packet is converted into an IR-DYN packet andthe IR-DYN packet may be transmitted in the same order within the packetstream in place of an original IR packet.

Mode #3 (t6020) refers to a mode in which IR and IR-DYN packets aredetected from a compressed packet stream to extract context information.A static chain and a dynamic chain may be extracted from the IR packetand a dynamic chain may be extracted from the IR-DYN packet. Afterextraction, the IR and IR-DYN packets are converted into normalcompression packets. The converted packets may be transmitted in thesame order within the packet stream in place of original IR and IR-DYNpackets.

In each mode, the context information is extracted and the remainingpackets may be encapsulated and transmitted according to the link layerpacket structure for the compressed IP packets. The context informationmay be encapsulated and transmitted according to the link layer packetstructure for signaling information, as link layer signaling.

The extracted context information may be included in a RoHC-Udescription table (RDT) and may be transmitted separately from the RoHCpacket flow. Context information may be transmitted through a specificphysical data path along with other signaling information. The specificphysical data path may mean one of normal PLPs, a PLP in which low levelsignaling (LLS) is delivered, a dedicated PLP or an L1 signaling path.Here, the RDT may be context information (static chain and/or dynamicchain) and/or signaling information including information associatedwith header compression. In some embodiments, the RDT shall betransmitted whenever the context information is changed. In addition, insome embodiments, the RDT shall be transmitted every physical frame. Inorder to transmit the RDT every physical frame, the previous RDT may bereused.

The receiver may select a first PLP and first acquire signalinginformation of the SLT, the RDT, the LMT, etc., prior to acquisition ofa packet stream. When signaling information is acquired, the receivermay combine the signaling information to acquire mapping betweenservice-IP information-context information-PLP. That is, the receivermay check which service is transmitted in which IP streams or which IPstreams are delivered in which PLP and acquire context information ofthe PLPs. The receiver may select and decode a PLP carrying a specificpacket stream. The adaptation module may parse context information andcombine the context information with the compressed packets. To thisend, the packet stream may be restored and delivered to the RoHCdecompressor. Thereafter, decompression may start. At this time, thereceiver may detect IR packets to start decompression from an initiallyreceived IR packet (mode 1), detect IR-DYN packets to startdecompression from an initially received IR-DYN packet (mode 2) or startdecompression from any compressed packet (mode 3).

Hereinafter, packet encapsulation will be described.

The link layer protocol may encapsulate all types of input packets suchas IP packets, TS packets, etc. into link layer packets. To this end,the physical layer processes only one packet format independently of theprotocol type of the network layer (here, an MPEG-2 TS packet isconsidered as a network layer packet). Each network layer packet orinput packet is modified into the payload of a generic link layerpacket.

In the packet encapsulation procedure, segmentation may be used. If thenetwork layer packet is too large to be processed in the physical layer,the network layer packet may be segmented into two or more segments. Thelink layer packet header may include fields for segmentation of thetransmission side and recombination of the reception side. Each segmentmay be encapsulated into the link layer packet in the same order as theoriginal location.

In the packet encapsulation procedure, concatenation may also be used.If the network layer packet is sufficiently small such that the payloadof the link layer packet includes several network layer packets,concatenation may be performed. The link layer packet header may includefields for performing concatenation. In concatenation, the input packetsmay be encapsulated into the payload of the link layer packet in thesame order as the original input order.

The link layer packet may include a header and a payload. The header mayinclude a base header, an additional header and/or an optional header.The additional header may be further added according to situation suchas concatenation or segmentation and the additional header may includefields suitable for situations. In addition, for delivery of theadditional information, the optional header may be further included.Each header structure may be pre-defined. As described above, if theinput packets are TS packets, a link layer header having packetsdifferent from the other packets may be used.

Hereinafter, link layer signaling will be described.

Link layer signaling may operate at a level lower than that of the IPlayer. The reception side may acquire link layer signaling faster thanIP level signaling of the LLS, the SLT, the SLS, etc. Accordingly, linklayer signaling may be acquired before session establishment.

Link layer signaling may include internal link layer signaling andexternal link layer signaling. Internal link layer signaling may besignaling information generated at the link layer. This includes theabove-described RDT or the below-described LMT. External link layersignaling may be signaling information received from an external module,an external protocol or a higher layer. The link layer may encapsulatelink layer signaling into a link layer packet and deliver the link layerpacket. A link layer packet structure (header structure) for link layersignaling may be defined and link layer signaling information may beencapsulated according to this structure.

FIG. 7 is a diagram showing a link mapping table (LMT) according to oneembodiment of the present invention.

The LMT may provide a list of higher layer sessions carried through thePLP. In addition, the LMT may provide additional information forprocessing link layer packets carrying the higher layer sessions. Here,the higher layer session may also be referred to as multicast.

Information on IP streams or transport sessions transmitted through aspecific PLP may be acquired through the LMT. In contrast, informationon through which PLP a specific transport session is delivered may beacquired.

The LMT may be delivered in any PLP identified as carrying LLS. Here,the PLP in which the LLS is delivered may be identified by an LLS flagof L1 detail signaling information of a physical layer. The LLS flag maybe a flag field indicating whether the LLS is delivered in the PLP, eachPLP. Here, L1 detail signaling information may correspond to thebelow-described PLS2 data.

That is, the LMT may be delivered in the same PLP along with the LLS.Each LMT shall describe mapping between PLPs and IP addresses/ports asdescribed above. As described above, the LLS may include an SLT and theIP address/port described in the LMT may be any IP address/portassociated with any service described in the SLT delivered in the samePLP as the LMT.

In some embodiments, the PLP identifier information in theabove-described SLT, SLS, etc. may be used to confirm informationindicating through which PLP a specific transport session indicated bythe SLT or SLS is transmitted may be confirmed.

In another embodiment, the PLP identifier information in theabove-described SLT, SLS, etc. will be omitted and PLP information ofthe specific transport session indicated by the SLT or SLS may beconfirmed by referring to the information in the LMT. In this case, thereceiver may combine the LMT and other IP level signaling information toidentify the PLP. Even in this embodiment, the PLP information in theSLT, SLS, etc. is not omitted and may remain in the SLT, SLS, etc.

The LMT according to the shown embodiment may include a signaling_typefield, a PLP_ID field, a num_session field and/or information on eachsession. Although the LMT of the shown embodiment describes IP streamstransmitted through one PLP, a PLP loop may be added to the LMT todescribe information on a plurality of PLPs in some embodiments. In thiscase, the LMT may describe, in a PLP loop, PLPs for any IP address/portassociated with any service described in the SLT delivered together, asdescribed above.

The signaling_type field may indicate the type of signaling informationdelivered by the table. The value of signaling_type field for the LMTmay be set to 0x01. The signaling_type field may be omitted. The PLP_IDfield may identify a target PLP to be described. If the PLP loop isused, each PLP_ID field may identify each target PLP. The PLP_ID fieldand subsequent fields thereof may be included in the PLP loop. Thebelow-described PLP_ID field is an identifier for one PLP of the PLPloop and the below-described fields may be fields for the correspondingPLP.

The num_session field may indicate the number of higher layer sessionsdelivered through the PLP identified by the corresponding PLP_ID field.

According to the number indicated by the num_session field, informationon each session may be included. This information may include asrc_IP_add field, a dst_IP_add field, a src_UDP_port field, adst_UDP_port field, an SID_flag field, a compressed_flag field, an SIDfield and/or a context_id field.

The src_IP_add field, the dst_IP_add field, the src_UDP_port field andthe dst_UDP_port field may indicate the source IP address, thedestination IP address, the source UDP port and the destination UDP portof the transport session among the higher layer sessions deliveredthrough the PLP identified by the corresponding PLP_ID field.

The SID_flag field may indicate whether the link layer packet deliveringthe transport session has an SID field in the optional header. The linklayer packet delivering the higher layer session may have an SID fieldin the optional header and the SID field value may be equal to that ofthe SID field in the LMT.

The compressed_flag field may indicate whether header compression isapplied to the data of the link layer packet delivering the transportsession. In addition, presence/absence of the below-described context_idfield may be determined according to the value of this field. If headercompression is applied (compressed_flag=1), the RDT may be present andthe PLP ID field of the RDT may have the same value as the PLP_ID fieldassociated with this compressed_flag field.

The SID field may indicate the SIDs (sub stream IDs) of the link layerpackets delivering the transport session. These link layer packets mayinclude SIDs having the same values as this SID field in the optionalheader thereof. To this end, the receiver may filter link layer packetsusing LMT information and the SID information of the link layer packetheader, without parsing all link layer packets.

The context_id field may provide a reference for a context id (CID) inthe RDT. The CID information of the RDT may indicate the context ID ofthe compression IP packet stream. The RDT may provide contextinformation of the compression IP packet stream. Through this field, theRDT and the LMT may be associated.

In the above-described embodiments of the signaling information/table ofthe present invention, the fields, elements or attributes may be omittedor may be replaced with other fields. In some embodiments, additionalfields, elements or attributes may be added.

In one embodiment of the present invention, service components of oneservice may be delivered through a plurality of ROUTE sessions. In thiscase, an SLS may be acquired through bootstrap information of an SLT. AnS-TSID and an MPD may be referenced through the USBD of the SLS. TheS-TSID may describe not only the ROUTE session delivered by the SLS butalso transport session description information of another ROUTE sessioncarried by the service components. To this end, the service componentsdelivered through the plurality of ROUTE sessions may all be collected.This is similarly applicable to the case in which the service componentsof one service are delivered through a plurality of MMTP sessions. Forreference, one service component may be simultaneously used by theplurality of services.

In another embodiment of the present invention, bootstrapping of an ESGservice may be performed by a broadcast or broadband network. Byacquiring the ESG over broadband, URL information of the SLT may beused. ESG information may be requested using this URL.

In another embodiment of the present invention, one service component ofone service may be delivered over the broadcast network and the otherservice component may be delivered over broadband (hybrid). The S-TSIDmay describe components delivered over the broadcast network such thatthe ROUTE client acquires desired service components. In addition, theUSBD may have base pattern information to describe which segments (whichcomponents) are delivered through which path. Accordingly, the receivercan confirm a segment to be requested from the broadband service and asegment to be detected in a broadcast stream.

In another embodiment of the present invention, scalable coding of aservice may be performed. The USBD may have all capability informationnecessary to render the service. For example, when one service isprovided in HD or UHD, the capability information of the USBD may have avalue of “HD or UHD”. The receiver may check which component isreproduced in order to render the UHD or HD service using the MPD.

In another embodiment of the present invention, through a TOI field ofthe LCT packets delivered through the LCT channel delivering the SLS,which SLS fragment is delivered using the LCT packets (USBD, S-TSID,MPD, etc.) may be identified.

In another embodiment of the present invention, app components to beused for app based enhancement/an app based service may be deliveredover the broadcast network as NRT components or may be delivered overbroadband. In addition, app signaling for app based enhancement may beperformed by an application signaling table (AST) delivered along withthe SLS. In addition, an event which is signaling for operation to beperformed by the app may be delivered in the form of an event messagetable (EMT) along with the SLS, may be signaled in the MPD or may bein-band signaled in the form of a box within DASH representation. TheAST, the EMT, etc. may be delivered over broadband. App basedenhancement, etc. may be provided using the collected app components andsuch signaling information.

In another embodiment of the present invention, a CAP message may beincluded and provided in the above-described LLS table for emergencyalert. Rich media content for emergency alert may also be provided. Richmedia may be signaled by a CAP message and, if rich media is present,the rich media may be provided as an EAS service signaled by the SLT.

In another embodiment of the present invention, linear servicecomponents may be delivered over the broadcast network according to theMMT protocol. In this case, NRT data (e.g., app components) of theservice may be delivered over the broadcast network according to theROUTE protocol. In addition, the data of the service may be deliveredover broadband. The receiver may access the MMTP session delivering theSLS using the bootstrap information of the SLT. The USBD of the SLSaccording to the MMT may reference the MP table such that the receiveracquires linear service components formatted into the MPU deliveredaccording to the MMT protocol. In addition, the USBD may furtherreference the S-TSID such that the receiver acquires NRT data deliveredaccording to the ROUTE protocol. In addition, the USBD may furtherreference the MPD to provide a reproduction description of datadelivered over broadband.

In another embodiment of the present invention, the receiver may deliverlocation URL information capable of acquiring a file content item (file,etc.) and/or a streaming component to a companion device through a websocket method. The application of the companion device may acquirecomponents, data, etc. through a request through HTTP GET using thisURL. In addition, the receiver may deliver information such as systemtime information, emergency alert information, etc. to the companiondevice.

FIG. 8 illustrates a configuration of a broadcast signal transmissionapparatus for future broadcast services according to an embodiment ofthe present invention.

The broadcast signal transmission apparatus for future broadcastservices according to the present embodiment may include an inputformatting block 1000, a bit interleaved coding & modulation (BICM)block 1010, a frame building block 1020, an OFDM generation block 1030and a signaling generation block 1040. Description will be given of anoperation of each block of the broadcast signal transmission apparatus.

In input data according to an embodiment of the present invention, IPstream/packets and MPEG2-TS may be main input formats, and other streamtypes are handled as general streams.

The input formatting block 1000 may demultiplex each input stream intoone or a plurality of data pipes, to each of which independent codingand modulation are applied. A DP is the basic unit for robustnesscontrol, which affects QoS. One or a plurality of services or servicecomponents may be carried by one DP. The DP is a logical channel in aphysical layer for delivering service data or related metadata capableof carrying one or a plurality of services or service components.

Since QoS depends on characteristics of a service provided by thebroadcast signal transmission apparatus for future broadcast servicesaccording to the embodiment of the present invention, data correspondingto respective services needs to be processed using different schemes.

BICM block 1010 may include a processing block for a profile (or system)to which MIMO is not applied, and a processing block for a profile (orsystem) to which MIMO is applied and may comprise a plurality blocks forprocessing each Data Pipe.

A processing block of the BICM block to which MIMO is not applied mayinclude a data FEC encoder, a bit interleaver, a constellation mapper, asignal space diversity (SSD) encoding block and a time interleaver. Aprocessing block of the BICM block to which MIMO is applied may isdistinguished from the processing block of the BICM block to which MIMOis not applied in that the processing block further includes a cell-worddemultiplexer and a MIMO encoding block

The data FEC encoder performs FEC encoding on an input BBF to generateFECBLOCK procedure using outer coding (BCH) and inner coding (LDPC). Theouter coding (BCH) is optional coding method. The bit interleaver mayinterleave outputs of the data FEC encoder to achieve optimizedperformance with a combination of LDPC codes and a modulation schemewhile providing an efficiently implementable structure. A detailedoperation of the bit interleaver will be described later.

The constellation mapper may modulate each cell word from the bitinterleaver or the cell-word demultiplexer in the advanced profile usingeither QPSK, QAM-16, non-uniform QAM (NUQ-64, NUQ-256, or NUQ-1024) ornon-uniform constellation (NUC-16, NUC-64, NUC-256, or NUC-1024) mappingto give a power-normalized constellation point. This constellationmapping is applied only for DPs. It is observed that QAM-16 and NUQs aresquare shaped, while NUCs have arbitrary shapes. Both NUQs and NUCs aredefined specifically for each code rate and the particular one used issignaled by the parameter DP_MOD field in the PLS2 data. The timeinterleaver may operates at a DP level. Parameters of time interleaving(TI) may be set differently for each DP. The time interleaver accordingto an embodiment of the present invention can be positioned between aBICM chain block and a frame builder.

Here, The time interlaever according to an embodiment of the presentinvention can use both a convolutional interleaver (CI) and a blockinterleaver (BI) or selectively using either the CI or the BI accordingto a physical layer pipe (PLP) mode. A PLP according to an embodiment ofthe present invention is a physical path corresponding to the sameconcept as that of the above-described DP, and a name of the PLP may bechanged by a designer. A PLP mode according to an embodiment of thepresent invention may include a single PLP mode or a multi-PLP modeaccording to the number of PLPs processed by a broadcast signaltransmitter or a broadcast signal transmission apparatus. In the presentinvention, time interleaving in which different time interleavingschemes are applied according to PLP modes may be referred to as hybridtime interleaving.

The hybrid time interleaver may include a BI and a CI. That is, whenPLP_NUM=1, the BI is not applied (BI is turned OFF) and only the CI isapplied. When PLP_NUM>1, both the BI and the CI may be applied (BI isturned ON). A structure and an operation of the CI applied whenPLP_NUM>1 may be different from a case of PLP_NUM=1. The hybrid timedeinterleaver may perform an operation corresponding to an inverseoperation of the hybrid time interleaver described above.

The cell-word demultiplexer is used for dividing a single cell-wordstream into dual cell-word streams for MIMO processing. The MIMOencoding block may process an output of the cell-word demultiplexerusing a MIMO encoding scheme. The MIMO encoding scheme of the presentinvention may be defined as full-rate spatial multiplexing (FR-SM) toprovide capacity increase with relatively small complexity increase atthe receiver side. MIMO processing is applied at the DP level. NUQ (e1,iand e2,i) corresponding to a pair of constellation mapper outputs is fedto an input of a MIMO encoder and paired MIMO encoder output (g1,i andg2,i) is transmitted by the same carrier k and OFDM symbol l ofrespective TX antennas thereof.

The frame building block 1020 may map the data cells of the input DPsinto the OFDM symbols within a frame, and perform frequency interleavingfor frequency-domain diversity.

A frame according to an embodiment of the present invention is furtherdivided into a preamble, one or more frame signaling symbols (FSSs),normal data symbols. The preamble provides a set of basic transmissionparameters for efficient transmission and reception of a signal. And thepreamble indicates whether the emergency alert service (EAS) is providedin a current frame or not. A main purpose of the FSS is to carry PLSdata. For fast synchronization and channel estimation, and hence fastdecoding of PLS data, the FSS has a dense pilot pattern than a normaldata symbol.

The frame building block 1020 may include a delay compensation block foradjusting timing between DPs and corresponding PLS data to ensure thatthe DPs and the corresponding PLS data are co-timed at a transmitterside, a cell mapper for mapping PLS, DPs, auxiliary streams, dummycells, etc. to active carriers of the OFDM symbols in the frame and afrequency interleaver.

The frequency interleaver may randomly interleave data cells receivedfrom the cell mapper to provide frequency diversity. In addition, thefrequency interleaver may operate on data corresponding to an OFDMsymbol pair including two sequential OFDM symbols or an OFDM symbolusing a different interleaving-seed order to obtain maximum interleavinggain in a single frame.

The OFDM generation block 1030 modulates OFDM carriers by cells producedby the frame building block, inserts pilots, and produces a time domainsignal for transmission. In addition, this block subsequently insertsguard intervals, and applies peak-to-average power ratio (PAPR)reduction processing to produce a final RF signal.

The signaling generation block 1040 may create physical layer signalinginformation used for an operation of each functional block. Signalinginformation according to an embodiment of the present invention mayinclude PLS data. The PLS data includes PLS1 data and PLS2 data.

The PLS1 data is a first set of PLS data carried in an FSS symbol in aframe having a fixed size, coding and modulation, which carries basicinformation about the system in addition to the parameters needed todecode the PLS2 data. The PLS1 data provides basic transmissionparameters including parameters required to enable reception anddecoding of the PLS2 data. In addition, the PLS1 data remains constantfor the duration of a frame group.

The PLS2 data is a second set of PLS data transmitted in an FSS symbol,which carries more detailed PLS data about the system and the DPs. ThePLS2 contains parameters that provide sufficient information for thereceiver to decode a desired DP. The PLS2 signaling further includes twotypes of parameters, PLS2 static data (PLS2-STAT data) and PLS2 dynamicdata (PLS2-DYN data). The PLS2 static data is PLS2 data that remainsstatic for the duration of a frame group and the PLS2 dynamic data isPLS2 data that dynamically changes frame by frame.

PLS2 data can include FIC_flag information. FIC (fast informationchannel) is a dedicated channel for carrying cross-layer information toenable fast service acquisition and channel scanning FIC_FLAG is a 1-bitfield and indicates whether the FIC is used in a current frame. If thisfield is set to ‘1’, the FIC is provided in the current frame. If thisfield set to ‘0’, the FIC is not carried in the current frame.

The BICM block 1010 may include BICM block for protection of the PLSdata including a PLS FEC encoder, a bit interleaver and a constellationmapper.

The PLS FEC encoder may include a scrambler for scrambling PLS1 data andPLS2 data, a BCH encoding/zero insertion block for outer encoding on thescrambled PLS1,2 data using a shortened BCH code for PLS protection, andinsert zero bits after BCH encoding, an LDPC encoding block for LDPCencoding using an LDPC code and an LDPC parity punturing block. The bitinterleaver may interleave each of shortened and punctured PLS1 data andPLS2 data. The constellation mapper may map the bit-interleaved PLS1data and PLS2 data to constellations.

The broadcast signal reception apparatus for future broadcast servicesaccording to the embodiment of the present invention may correspond tothe broadcast signal transmission apparatus for future broadcastservices described with reference to FIG. 8.

The broadcast signal reception apparatus for future broadcast servicesaccording to the embodiment of the present invention may include asynchronization & demodulation module carrying out demodulationcorresponding to a reverse procedure of a procedure performed by thebroadcast signal transmission apparatus, a frame parsing module parsinginput signal frames and extracting data through which a service selectedby a user is transmitted, a demapping & decoding module which convertinput signals into bit domain data and then deinterleave the same asnecessary, perform demapping of mapping applied for transmissionefficiency and correct an error generated on a transmission channelthrough decoding, an output processor performing reverse procedures ofvarious compression/signal processing procedures which are applied bythe broadcast signal transmission apparatus and a signaling decodingmodule obtaining PLS information from a signal demodulated by thesynchronization & demodulation module.

The frame parsing module, the demapping & decoding module and the outputprocessor may execute functions thereof using data output from thesignaling decoding module.

According to an embodiment of the present invention, each TI group iseither mapped directly to one frame or spread over PI frames. Each TIgroup is also divided into more than one TI block (NTI), where each TIblock corresponds to one usage of a time interleaver memory. The TIblocks within the TI group may contain slightly different numbers ofXFECBLOCKs. Typically, the time interleaver may also function as abuffer for DP data prior to a process of frame building.

The Time interleaving according to an embodiment of the presentinvention is a twisted row-column block interleaver. The twistedrow-column block interleaver according to an embodiment of the presentinvention may column-wise write a first XFECBLOCK into a first column ofa TI memory, and a second XFECBLOCK into a next column, and so on).Then, in an interleaving array, cells are diagonal-wise readdiagonal-wise from a first row (rightwards along a row beginning with aleft-most column) to a last row, Nr cells are read out

Moreover, in order to achieve single-memory deinterleaving at a receiverside regardless of a number of XFECBLOCKs in a TI block the twistedrow-column block interleaver may insert the virtual XFECBLOCKs into theTI memory. The virtual XFECBLOCKs must be inserted in front of otherFECBLOCKS to achieve single-memory deinterleaving at a receiver side.

FIG. 9 illustrates a write operation of a time interleaver according toan embodiment of the present invention.

A left block in the figure illustrates a TI memory address array, andright blocks in the figure illustrate a write operation when two virtualFEC blocks and one virtual FEC block are inserted into heads of twocontiguous TI groups, respectively.

The frequency interleaver according to the present embodiment mayinclude an interleaving address generator for generating an interleavingaddress for applying corresponding data to a symbol pair.

FIG. 10 illustrates an interleaving address generator including a mainpseudo-random binary sequence (PRBS) generator and a sub-PRBS generatoraccording to each FFT mode which are included in a frequency interleaveraccording to an embodiment of the present invention.

(a) shows the block diagrams of the interleaving-address generator for8K FFT mode, (b) shows the block diagrams of the interleaving-addressgenerator for 16K FFT mode and (c) shows the block diagrams of theinterleaving-address generator for 32K FFT mode.

The interleaving process for the OFDM symbol pair is described asfollows, exploiting a single interleaving-sequence. First, availabledata cells (the output cells from the Cell Mapper) to be interleaved inone OFDM symbol O_(m,1) is defined as O_(m,1)=[x_(m,1,0), . . . ,x_(m,1,p), . . . , x_(m,1,Ndata-1)] for l=0, . . . , N_(sym)-1, wherex_(m,1,p) is the p^(th) cell of the l^(th) OFDM symbol in the m^(th)frame and N_(data) is the number of data cells: N_(data)=C_(FSS) for theframe signaling symbol(s), N_(data)=C_(data) for the normal data, andN_(data)=C_(FES) for the frame edge symbol. In addition, the interleaveddata cells are defined as P_(m,1)=[v_(m,1,0), . . . , v_(m,1,Ndata-1)]for l=0, . . . , N_(sym)-1.

For the OFDM symbol pair, the interleaved OFDM symbol pair is given byv_(m,1,Hi(p))=x_(m,1,p), p=0, . . . , N_(data)-1, for the first OFDMsymbol of each pair v_(m,1,p)=x_(m,1,p)=x_(m,1,Hi(p)), p=0, . . . ,N_(data)-1 for the second OFDM symbol of each pair, where H_(l)(p) isthe interleaving address generated based on a PRBS generator and acyclic shift value (symbol offset) of a sub-PRBS generator.

FIG. 11 is a diagram of an apparatus for processing a broadcast serviceaccording to an aspect of the present invention.

According to an aspect, the present invention may be related to thebroadcast service processing apparatus. The broadcast service processingapparatus may receive service data and/or signaling information of abroadcast service and may communicate with an application toappropriately provide a corresponding broadcast service.

In detail, the broadcast service processing apparatus may receive abroadcast signal having service data and/or signaling information,receive a request for on screen message notification (OSN) informationusing API from an application, generate an answer for acquisition of theOSN in response to the API, and transmit the answer to the correspondingapplication.

The broadcast service processing apparatus according to the presentinvention may include a tuner and/or a processor as an internal/externalcomponent. Here, the processor may be a hardware processor.

The tuner may receive a broadcast signal. The broadcast signal mayinclude service data of a broadcast service and/or signaling informationfor signaling the corresponding broadcast service. The signalinginformation may further include OSN information. The OSN may indicatebroadcaster's preference about whether video images of a broadcastservice are capable of being hidden by another application. That is, theOSN information may indicate whether it is fine that video of abroadcast service at a time point is hidden by an application, othergraphic overlay, and so on.

The processor may acquire the service data and/or the signalinginformation from the broadcast signal to provide the broadcast service.The processor may provide an application environment in which anapplication is executable in the broadcast service processing apparatus.Here, the application may be executed by the broadcast serviceprocessing apparatus.

The processor may communicate with an application through an applicationprogramming interface (API) or the like. The processor may receive arequest based on a uniform resource locator (URL) request API from theapplication. Here, the URL request API may be an API for making arequest for signaling metadata or the like from the broadcast serviceprocessing apparatus. In some embodiments, the URL request API may be anAPI for making a request or a URL for referencing latest acquired OSN.

The processor may generate an object for response to the URL requestAPI. In some embodiments, the objet may be a JavaScript object notation(JSON) object. The JSON object may be referred to as a first JSON objectin some embodiments. The first JSON object may include a URL for therequested signaling metadata. In some embodiments, the first JSON objectmay include a URL for the requested OSN.

Then, the processor may transmit the first JSON object to theapplication in response to the URL request API.

In a broadcast service processing apparatus according to an embodimentof the present invention, the processor may further insert timeinformation into the first JSON object while generating the first JSONobject. The time information may indicate a time point of receivingmetadata requested by the API. In some embodiments, the time informationmay indicate a time point of receiving the requested OSN.

In a broadcast service processing apparatus according to anotherembodiment of the present invention, the processor may receive asubscription request based on the signaling change subscribe API. Here,the signaling change subscribe API may be referred to as a second API.The signaling change subscribe API may be an API issued in the broadcastservice processing apparatus by an application to signal notification tothe application when metadata requested by the corresponding API ischanged. Here, in some embodiments, the requested metadata may be OSN.

In a broadcast service processing apparatus according to anotherembodiment of the present invention, the signaling change subscribe APImay include a second JSON object. The second JSON object may includeinformation for making a request for notification. The information maybe used to signal notification to the application by the broadcastservice processing apparatus when the broadcast service processingapparatus receives a new version or updated version of the requestedmetadata. Here, in some embodiments, the requested metadata may be OSN.

In a broadcast service processing apparatus according to anotherembodiment of the present invention, the processor may issue thesignaling change notification API to transmit notification to theapplication that makes a request for subscription. Here, the signalingchange notification API may be referred to as a third API. The signalingchange notification API may be an API for notifying an application aboutchange in the metadata requested by the corresponding API. Here, in someembodiments, the requested metadata may be OSN.

In a broadcast service processing apparatus according to anotherembodiment of the present invention, the aforementioned signaling changenotification API may include a third JSON object. The third JSON objectmay include a URL for referencing new or updated metadata and/orinformation indicating a time point of receiving the corresponding newor updated metadata. Here, in some embodiments, the requested metadatamay be OSN.

In a broadcast service processing apparatus according to anotherembodiment of the present invention, an application and the broadcastservice processing apparatus may communicate with each other through aweb socket protocol.

In a broadcast service processing apparatus according to anotherembodiment of the present invention, the processor may receive anunsubscription request according to the signaling change unsubscribe APIfrom the application. The application that transmits the subscriptionrequest by the aforementioned signaling change subscribe API may make arequest for unsubscription via the signaling change unsubscribe API.

In a broadcast service processing apparatus according to anotherembodiment of the present invention, the broadcast service processingapparatus and/or the application may transmit and signal a URL foraccess to OSN and make a request for subscription and unsubscription.

In a broadcast service processing apparatus according to embodiments ofthe present invention, an application may check that OSN is transmittedto a broadcast service processing apparatus of a receiver side even ifthe application is arbitrarily terminated or hidden.

In a broadcast service processing apparatus according to embodiments ofthe present invention, an application may accurately recognize a timeperiod for clearing a screen through reception visual information ofOSN.

In a broadcast service processing apparatus according to embodiments ofthe present invention, a broadcast application or a native applicationof a receiver may share corresponding signaling information, metadata,and/or the aforementioned contents through the aforementioned API, andso on, thereby reducing an entire required bandwidth.

The aforementioned broadcast service processing apparatuses according toembodiments of the present invention may be combined. The aforementionedinternal/external components of the broadcast service processingapparatus according to the present invention may be added, changed,replaced, or deleted in some embodiments. The aforementionedinternal/external components of the broadcast service processingapparatus may be embodied as a hardware component.

A next-generation broadcast system and a broadcast service processingapparatus based thereon may provide a broadcast service in the form of acombination of broadcasting and a network. That is, the next-generationbroadcast system may show an application to a user to allow the user andbroadcasting to interact with each other through the application and,accordingly, the user may experience much content as possible.

An application may be launched in a broadcast service processingapparatus, for example, a TV. In some embodiments, applicationoperations according to the present invention may also be applied to TVswith different platforms. In some embodiments, a web socket protocol maybe used as an interface between a broadcast service processing apparatusand an application. In some embodiments, data transmitted and receivedbetween the broadcast service processing apparatus and the applicationmay be in the form of JSON-RPC.

The application may be interested in signaling information or metadatathat is distributed and transmitted according to the aforementionednext-generation broadcast system. For example, signaling informationsuch as AEAT, MPD, and OSN may require an application. The signalinginformation may be relatively rapidly changed in consideration of a lifecycle and, accordingly, these changes need to be signaled to theapplication.

In some embodiments, the application may use a CD web socket API definedto be used by a companion device (CD). However, there is a limit in anapplication uses an API for the CD or the CD uses an API for anapplication. For example, the broadcast service processing apparatus maywant to know whether web socket connection is achieved by an applicationor a CD but an API defined for the CD may not provide this function. Areceiver manufacturer may not want to support both an interactiveenvironment and the CD API. The CD interface may ask the receiver toreformat signaling data to JSON format friendly to JavaScript. This maycause a burden for converting binary and/or XML form of metadata intoJSON format. For application content, the application may poll through aHEAD request to an application context cache hierarchy but this isineffective.

Accordingly, the application may require an API or the like foracquiring corresponding signaling information or knowing whether theinformation is updated. In addition, when new or updated files arecompletely received through a broadcast network or is available by anapplication context cache, the application may also require an API forknowing the reception. The application may require an API for knowingextended content referenced by AEAT.

In a next-generation broadcast system, a signaling fragment that is OSNmay be transmitted to a broadcast service processing apparatus of areceiver side. The OSN may indicate the broadcaster's preference for thereceiver to avoid obscuring any part of the video images. For example,when important text or visual information such as emergency warningalert is inserted into video, a broadcaster may prefer not to hide thevideo. When a KeepScreenClear element of OSN has a ‘true’ value, thereceiver may prevent an application from using a video screen resource.The application may recognize this state to facilitate effectiveprovision of a broadcast service. The OSN may be signaling informationand may be transmitted to a receiver side through a broadcast signal.

A broadcast service processing apparatus of a receiver side transmitsimportant data of audio/video such as disaster broadcast to abroadcaster through OSN for a predetermined time period and, thus, thebroadcaster may transmit a message not to hide an image by a broadcastapplication or the like for the corresponding time period.

According to the present invention, even if the broadcast serviceprocessing apparatus receives signaling information such as OSN, theapparatus may notify an application about the information or define anAPI for allowing the application to know the information through arequest. The signaling information may further include MPD and/or AEAT.The AEAT may be signaling information including information onemergency. In some embodiments, all other available contents received bythe receiver as well as the signaling information may also betransmitted to the application through the API.

The present invention may define APIs for allowing the application toacquire information about whether the broadcast service processingapparatus of the receiver side transmits OSN and information on a statethereof.

For reference, the aforementioned APIs may not provide information on aform of a corresponding URL or a place including referenced content orsignaling. In general, files or metadata items may be present in thesame level on application context cache hierarchy. Broadcast servicesmay share ROUTE sessions and, thus, AEA enhancement content may beincluded in a broadcast service that intends to use the content. Thecontent is available by application context cache hierarchy and abroadcaster may take a measurement to prevent collision between the AEAenhancement content and the application content. The prevention may beachieved by preparing a separate AEA directory in content cachehierarchy.

In some embodiments, the application may comply with<baseURL>/<Content-Location> to access an application, applicationcontent, or AEA enhancement content on the application context cachehierarchy. However, the application may access MPD, AEAT, and OSNthrough only a URL acquired by the aforementioned URL request API or thelike to access the MPD, the AEAT, or and the OSN.

In some embodiments, the application may transmit a HTTP request to aURL provided by the aforementioned APIs to access related content and/orsignaling information. In this case, the MPD, the AEAT, and/or the OSNmay have a raw form transmitted from a broadcast network. That is, thereceiver may receive corresponding signaling information items through abroadcast network and transmit the information items without changeirrespective of format such as XML and a binary. Then, the applicationmay parse the corresponding signaling information according to types toacquire the parsed information.

FIG. 12 is a diagram a URL request API according to an embodiment of thepresent invention.

The URL request API according to the present invention may be an APIissued to a broadcast service processing apparatus by an application forallowing the application to acquire a URL for obtaining predeterminedcontent or signaling metadata.

The application may intent to access various contents and/or signalingmetadata items transmitted to a broadcast network or the like. The URLrequest API may return a list of URLs available by the application tothe application. Here, the URL request API may be referred to as acontent and signaling URL request API (Query Content and Signaling URLAPI). Here, the URLs may be, for example, a URL for acquisition ofspecific content and/or signaling metadata, requested by an applicationvia XHR. In some embodiments, when content and/or metadata is not AEATand/or OSN applied to all broadcast services, only references (URL)related to a current broadcast service may be returned to theapplication.

In the illustrated embodiment of the URL request API, the URL requestAPI may be defined as “org.atsc.query.ObjectUrl”. The API may include aJSON object 12010 as a parameter.

In detail, the JSON object 12010 may include objectNames.

The objectNames may be an array of content and/or signaling objects. TheobjectNames may be referred to as key and may be a required element.

The objectNames may include a list of listed values. The list mayinclude values such as MPD, AEAT, OSN, and Content. When the list isempty, the corresponding API may make a request for all of the MPD, theAEAT, the OSN, and the Content.

When the MPD value is included, the value may be used to make a requestfor the most recent MPD of a current broadcast service. When the AEATvalue is included, the value may be used to make a request for the mostAEAT. When the OSN value is included, the value may be used to make arequest for the most OSN. When the Content value is included, the valuemay be used to make a request for a list of URLs for acquisition of AEAenhancement content and/or application associated with an applicationcontext ID.

In response to the URL request API, the broadcast service processingapparatus may return a JSON object 12020 to an application.

In detail, the JSON object 12020 may include urlList.

The urlList may be a list of references, i.e., URLs. The urlList may berequired element. The urlList may include objectName, contentType,objectUrl, and/or receiveTime.

The objectName may be one of content and/or signaling object name. Thenames may be one of MPD, AEAT, OSN, and Content. The objectUrlcorresponding to the objectName may be a URL used to access dataaccording to objectName of a corresponding broadcast service.

The contentType may provide a content type of an object referenced bythe objectUrl. The contentType may be an optional parameter. Theapplication may determine whether the corresponding referenced contentobject is a wanted object using a content type of an object. AcontentType value may be a value that is extracted from content-typeattribute of EFDT or package information used to transmit contentwithout change.

The objectUrl may be a fully-qualified URL used by an application. TheURL may be used to acquire, for example, signaling metadata and/orcurrent broadcast content associated with the objectName for an XHRrequest.

The receiveTime may indicate a time point of receiving correspondingcontent and/or signaling object. In some embodiments, the time point maybe indicated by date and/or time information. The receiveTime needs tobe included in a JSON object when the signaling object is OSN. Here, anOSN table may include a Notification Duration field. The NotificationDuration field may indicate a duration time of a KeepScreenClear messageindicating that an image needs to be empty and the duration time may bestarted from a time point of receiving OSN. Accordingly, the time pointof receiving the OSN may be required to appropriately use the OSN by anapplication.

The aforementioned URL request APIs according to embodiments of thepresent invention may be combined. In a broadcast service processingapparatus according to embodiments of the present invention, a URLrequest API may be the URL request API according to the aforementionedembodiments.

FIG. 13 is a diagram showing an application example of a URL request APIaccording to the present invention.

In the illustrated application example of the URL request API, anapplication may issue a URL request API to a broadcast serviceprocessing apparatus (13010). The URL request API may be defined as“org.atsc.query.ObjectUrl”. In the application example, the URL requestAPI may make a request for AEAT, MPD, and OSN.

In response to the URL request API, the broadcast service processingapparatus may also return a JSON object to the application (13020). Inthe JSON object, urlList may include objectUrl information on MPD, AEAT,and OSN. As described above, with regard to the OSN, receiveTime may bea required element. Accordingly, the JSON object may further include“2017-01-01T23:54:59.590Z” that is a time point of receiving thecorresponding OSN, as a receiveTime value.

In some embodiments, the AEAT may have a form of the aforementioned LLStable. Accordingly, the application may use the AEAT in consideration ofbinary header data preceding an XML AEAT section.

FIG. 14 is a diagram showing a signaling change notification APIaccording to an embodiment of the present invention.

The signaling change notification API according to the present inventionmay be an API issued to an application by a broadcast service processingapparatus and, when subscribed content and/or signaling metadata ischanged, the signaling change notification API may be an API fornotifying the application about the change.

The signaling change notification API may be referred to as content andsignaling change notification API. In some embodiments, the signalingchange notification API may be issued by a currently executedapplication. The signaling change notification API may be issued whenthere is a change in a version of MPD, AEAT, OSN, and/or content filessubscribed by an application to receive the notification through asignaling change subscribe API to be described later. In someembodiments, reception of a new content file or signaling object may beconsidered as version change. A notification message according to thesignaling change notification API may include a list for referencing newor updated content and/or signaling metadata.

In the illustrated embodiment of the signaling change notification API,the signaling change notification API may be defined as“org.atsc.notify”. The API may include a JSON object as a parameter. TheJSON object may include urlList. The urlList may include objectName,contentType, objectUrl, and/or receiveTime.

In response to the aforementioned URL request API, the illustrated JSONobject may be the same as the JSON object 12020 transmitted to theapplication. The urlList, objectName, contentType, objectUrl, and/orreceiveTime in the JSON object may also have the same meaning as theaforementioned information items of the JSON object 12020.

In some embodiments, when the JSON object is transmitted to theapplication according to the signaling change notification API, theapplication may not respond thereto. Accordingly, ‘id’ information maybe omitted from the JSON object. This is because that is no procedure ofa request and a response thereto.

The aforementioned signaling change notification APIs according toembodiments of the present invention may be combined. In a broadcastservice processing apparatus according to embodiments of the presentinvention, a signaling change notification API may be the aforementionedsignaling change notification API according to the embodiments.

FIG. 15 is a diagram showing an application example of a signalingchange notification API according to the present invention.

In the illustrated application example of a signaling changenotification API (15010), a broadcast service processing apparatus mayissue a signaling change notification API to an application. Thereby,the broadcast service processing apparatus may notify the applicationabout reception of a new MPD. The signaling change notification API maybe defined as “org.atsc.notify”. In the application example, a URL listof the signaling change notification API may include objectUrlinformation for acquisition of MPD.

In the illustrated application example of a signaling changenotification API (15020), a broadcast service processing apparatus mayissue a signaling change notification API to an application. Thereby,the broadcast service processing apparatus may notify the applicationabout reception of new AEAT and OSN. The signaling change notificationAPI may be defined as “org.atsc.notify”. In the application example, aURL list of the signaling change notification API may include objectUrlinformation items for acquisition of AEAT and OSN. As described above,with regard to the OSN, the receiveTime may be a required element.Accordingly, the JSON object may further include“2017-01-01T23:54:59.590Z” that is a time point of receiving thecorresponding OSN, as a receiveTime value.

Similarly, the AEAT may have a form of the aforementioned LLS table.Accordingly, the application may use the AEAT in consideration of binaryheader data preceding an XML AEAT section. In some embodiments, a prefixor the like of an “.lls” directory defined by the receiver may bedifferent from an application context cache determined by a receiveraccording to an embodiment of the present invention.

In the illustrated application example of a signaling changenotification API (15030), a broadcast service processing apparatus mayissue a signaling change notification API to an application. Thereby,the broadcast service processing apparatus may notify the applicationabout reception of a new version of various content files and/orsignaling metadata. The signaling change notification API may be definedas “org.atsc.notify”. In the application example, a URL list of thesignaling change notification API may include objectUrl informationitems for acquisition of app data of image/png, text/css, text/html, orthe like.

In some embodiments, upon receiving notification according to thesignaling change notification API, the application may select whetherthe application is reloaded or a portion thereof is reloaded.

FIG. 16 is a diagram showing an example of a signaling change subscribeAPI according to an embodiment of the present invention

The signaling change subscribe API according to the present inventionmay be an API issued to the broadcast service processing apparatus bayan application and, upon receiving new content and/or signaling metadataor new version of content and/or signaling metadata, the signalingchange subscribe API may be an API to be notified about the information.

When subscription is achieved, if the application receives new contentand/or signaling metadata or new version of content and/or signalingmetadata, the application may receive corresponding notification fromthe broadcast service processing apparatus. The signaling changesubscribe API may be referred to as content and signaling changesubscribe API (Subscribe Content and Signaling Changes API).

When there is any addition or version change, the broadcast serviceprocessing apparatus may issue the aforementioned signaling changenotification API to a subscribed application. The notification may becontinuously performed until subscription is canceled by the signalingchange unsubscribe API to be described later. The notification may becontinuously performed until a broadcast service is changed.

In the illustrated embodiment of a signaling change subscribe API(16010), the signaling change subscribe API may be defined as“org.atsc.subscribeObjectChange”. The API may include a JSON object16010 as a parameter.

In detail, the JSON object 16010 may include objectNames.

The objectNames may be an array of names of content and/or signalingobjects. The objectNames may be referred to as key and may be a requiredelement.

The objectNames may include a list of listed values. The list mayinclude values of MPD, AEAT, OSN, and Content. When the list is empty,the corresponding API may make a request for subscription of all of theMPD, the AEAT, the OSN, and the Content.

When the MPD value is included, if updated MPD of a current broadcastservice is received, the value may be used to make a request forsubscription for notification of the reception. When the AEAT value isincluded, if updated AEAT is received, the value may be used to make arequest for subscription for notification of the reception. When the OSNvalue is included, if updated OSN is received, the value may be used tomake a request for subscription for notification of the reception. Whenthe Content value is included, if new or updated application or AEAenhancement content is received, the value may be used to make a requestfor subscription for notification of the reception.

In the illustrated embodiment of a signaling change subscribe API(16020), an application may issue a signaling change subscribe API to abroadcast service processing apparatus. Thereby, the application maysubscribe for receiving notification when corresponding informationitems are updated or a new version is received with regard to ‘AEAT’,‘MPD’, and ‘Content’. That is, the application may subscribe to ‘AEAT’,‘MPD’, and ‘Content’ through the API.

In the illustrated embodiment of a signaling change subscribe API(16030), when subscription is successfully performed, the broadcastservice processing apparatus may transmit the illustrated message 16030as a response to the application.

As described above, when subscription is completed, upon receiving newor updated AEAT or the like, the broadcast service processing apparatus(broadcast receiver) may notify the application about the reception.Alternatively, when a predetermined file of an application context cacheis updated or added, the broadcast service processing apparatus may alsonotify the application about the updating or the addition.

In some embodiments, notification of the application or the AEAenhancement file may be performed after files are extracted from apackage and are checked for signaling. Here, application files may beapplication files matched with an application context ID and/or filtercodes.

The aforementioned signaling change subscribe APIs according toembodiments of the present invention may be combined. In a broadcastservice processing apparatus according to embodiments of the presentinvention, a signaling change subscribe API may be the aforementionedsignaling change subscribe API according to embodiments of the presentinvention.

FIG. 17 is a diagram showing a signaling change unsubscribe APIaccording to an embodiment of the present invention.

The signaling change unsubscribe API according to the present inventionmay be an API issued to a broadcast service processing apparatus and anAPI for unsubscription by the aforementioned signaling change subscribeAPI. The signaling change unsubscribe API may be referred to as contentand signaling change unsubscribe API (Unsubscribe Content and SignalingChanges API). Thereby, the application may stop receiving notificationof updating or addition of content and/or signaling.

In the illustrated embodiment of a signaling change unsubscribe API, thesignaling change unsubscribe API may be defined as“org.atsc.unsubscribeObjectChange”. The signaling change unsubscribe APImay include a JSON object 17010 as a parameter.

The JSON object 17010 may include objectNames.

The objectNames may be an array of names of content and/or signalingobjects. The objectNames may be referred to as key and may be a requiredelement.

The objectNames may include a list of listed values. The list mayinclude values of MPD, AEAT, OSN, Content, and the like. The applicationmay unsubscribe a signaling object or the like included in the list.When the list is empty, the corresponding API may unsubscribe all of theMPD, AEAT, OSN, and Content.

For example, when the MPD, the AEAT, and the OSN are included, theapplication may unsubscribe the MPD, the AEAT, and the OSN by adding theMPD, the AEAT, and the OSN to the list of the API.

In the illustrated application example of the signaling changeunsubscribe API (17020), an application may issue the signaling changeunsubscribe API to a broadcast service processing apparatus. Thesignaling change unsubscribe API may be defined as“org.atsc.unsubscribeObjectChange”. In the application example, the URLrequest API may make a request for unsubscription of AEAT.

When unsubscription is successfully performed, the broadcast serviceprocessing apparatus may transmit a message indicating thatunsubscription is successfully performed to the application as aresponse (17030). Here, “id” information may be matched with “id” of thesignaling change unsubscribe API.

Here, when the application subscribes a plurality of signaling objects,if the AEAT is unsubscribed via the aforementioned procedure,notification of other subscribed signaling objects except for the AEATmay be continuously performed.

In the illustrated embodiment of a signaling change subscribe API(17040), the application may issue a signaling change unsubscribe APIfor whole unsubscription to the broadcast service processing apparatus.As described above, in the application example, the list of JSON objectsmay be empty.

The aforementioned signaling change unsubscribe APIs according toembodiments of the present invention may be combined. In a broadcastservice processing apparatus according to embodiments of the presentinvention, a signaling change unsubscribe API may be the aforementionedsignaling change unsubscribe API according to embodiments of the presentinvention.

FIG. 18 is a diagram showing an OSN request API according to anembodiment of the present invention.

The OSN request API according to the present invention may be an APIissued to a broadcast service processing apparatus by an application andmay be an API for a query of whether the OSN of the broadcast serviceprocessing apparatus is transmitted and a state thereof. The broadcastservice processing apparatus may transmit elements of the OSN to theapplication according to the OSN request API and the application maydirectly infer whether a display is hidden.

A broadcast service processing apparatus (broadcast receiver) mayreceive an OSN fragment. The broadcast service processing apparatus maytransmit information of @notificationDuration, @kscFlag, and @versionrelated to a current service in the OSN along with receptionTime of theOSN to the application according to the API. The application may make arequest for information on a current OSN fragment to determine whether acurrent situation is appropriate to drive the application.

In the illustrated embodiment of an OSN request API, the OSN request APImay be defined as “org.atsc.query.onscreenMessageNotification”. Here, aparameter of the API may be omitted.

In this regard, the broadcast service processing apparatus may transmita response to the OSN request API to an application (18010). Theresponse may include a JSON object 18010.

The JSON object may include receptionTime, notificationDuration,kscFlag, and/or version.

The receptionTime may indicate a reception time of receivingcorresponding OSN information. The receptionTime may be a requiredelement.

The notificationDuration may indicate a duration time for clearing ascreen for important text/visual information of the screen. Here, startof the duration time may be the aforementioned receptionTime.

The kscFlag may indicate a state of screen clear. Here, the kscFlag mayindicate whether a screen is cleared according to true/false. In someembodiments, the broadcast service processing apparatus may alsotransmit corresponding information to the application at a time pointwhen the @kscFlag is back to a false value. In some embodiments, theapplication may directly query corresponding information to thebroadcast service processing apparatus to acquire correspondinginformation.

The version may indicate a version of a corresponding screen clear andscreen clear element of the OSN.

In the illustrated application example of the OSN request API (18020),the application may issue the OSN request API to a broadcast serviceprocessing apparatus. The OSN request API may be defined as“org.atsc.query.onscreenMessageNotification”.

In response to the OSN request API, the broadcast service processingapparatus may return the JSON object to the application (18030). TheJSON object may indicate a reception time of the OSN, duration time ofscreen clear, a state and a version of a screen clear, and the like.

The aforementioned OSN request APIs according to embodiments of thepresent invention may be combined. In a broadcast service processingapparatus according to embodiments of the present invention, the OSNrequest API may be the OSN request API according to the aforementionedembodiments of the present invention.

FIG. 19 is a diagram showing an OSN notification API according to anembodiment of the present invention.

The OSN notification API according to the present invention may be anAPI issued to an application by a broadcast service processing apparatusand may be an API for performing a procedure corresponding to theaforementioned OSN request API and a response thereto in the form ofnotification.

That is, the OSN notification API may allow the broadcast serviceprocessing apparatus to transmit information of @notificationDuration,@kscFlag, @version, and the like related to a current service in OSNand/or receptionTime of the OSN to the application. Here, the OSNnotification API may be referred to as an Onscreen Message ChangeNotification API.

In the illustrated embodiment of the OSN notification API (19010), theOSN notification API may be defined as “org.atsc.notify”. The API mayinclude a JSON object as a parameter.

The JSON object 19010 may further include msgType as well asreceptionTime, notificationDuration, kscFlag, and version elements ofthe aforementioned OSN request API.

The receptionTime, notificationDuration, kscFlag, and version elementsmay have the same meaning as in the aforementioned OSN request API. ThemsgType may indicate a signaling object indicated by content to betransmitted through a corresponding JSON object. Here, the msgType mayindicate OSN.

In some embodiments, when a JSON object is transmitted to theapplication according to the OSN notification API, the application maynot response thereto. Accordingly, ‘id’ information may be omitted fromthe JSON object.

In the illustrated application example of the OSN notification API(19020), the broadcast service processing apparatus may issue the OSNnotification API to the application. The API may be defined as“org.atsc.notify”. In the application example, the JSON object mayindicate reception time of the OSN, duration time of screen clear, astate and version of screen clear, and so on.

The aforementioned OSN notification APIs according to embodiments of thepresent invention may be combined. In a broadcast service processingapparatus according to embodiments of the present invention, the OSNnotification API may be the aforementioned OSN notification APIaccording to the aforementioned embodiment of the present invention.

FIG. 20 is a diagram showing a screen clean request API according to anembodiment of the present invention.

The screen clean request API according to the present invention may bean API issued to a broadcast service processing apparatus by anapplication and may be an API for query of whether a current screenstate is clear.

A flag indicating a state of a screen of the broadcast serviceprocessing apparatus may be defined and change in the corresponding flagmay be indicated to the application through a screen clean request APIand/or a screen clean notification API. When the screen clean requestAPI is used, the application may query a clear (clean) state of acurrent screen to acquire a value of the flag. When the screen cleannotification API is used, the broadcast service processing apparatus maynotify the application about the use whenever the clear state of thecurrent screen is changed. In this case, the aforementioned flag of thescreen clear state may be transmitted and, simultaneously, effectivetime information of the corresponding flag may also be transmitted.

In the illustrated embodiment of the screen clean request API, theapplication may issue the screen clean request API to the broadcastservice processing apparatus. The API may be defined as“org.atsc.query.screenClean”. A parameter of the API may be omitted.

In this regard, the broadcast service processing apparatus may transmita query to the screen clean request API to the application (20010). Theresponse may include a JSON object 20010.

The JSON object may include validFrom, validUntil, and/or clean.

The validFrom may indicate reception time of OSN of a receiver. In someembodiments, the validFrom may indicate a time point of a valid durationof a flag indicating the aforementioned screen clear state. That is, thecorresponding flag may be valid from a time point indicated by thevalidFrom.

The validUntil may indicate a time obtained by summing the receptiontime of the OSN and the aforementioned duration time of thenotificationDuration. In some embodiments, the validUntil may indicatean end time of a valid time of a flag indicating the aforementionedscreen clear state. That is, the corresponding flag may be valid up toonly a time point indicated by the validUntil.

The clean may indicate a corresponding flag value. That is, the cleanmay indicate a current state of screen clear.

In the illustrated application example of a screen clean request API(20020), an application may issue a screen clean request API to abroadcast service processing apparatus. The screen clean request API maybe defined as “org.atsc.query.screenClean”.

In response to the screen clean request API, the broadcast serviceprocessing apparatus may also return a JSON object to the application(20030). The JSON object may include the aforementioned clean flag. Itmay be seen that the flag is valid to “2017-01-01T23:59:59.590Z” from“2017-01-01T23:54:59.590Z”.

The aforementioned screen clean request APIs according to embodiments ofthe present invention may be combined. In a broadcast service processingapparatus according to embodiments of the present invention, a screenclean request API may be the aforementioned screen clean request APIaccording to embodiments of the present invention.

FIG. 21 is a diagram showing a screen clean notification API accordingto an embodiment of the present invention.

The screen clean notification API according to the present invention maybe an API issued to an application nay a broadcast service processingapparatus and may be an API for performing a procedure corresponding tothe aforementioned screen clean request API and a response thereto inthe form of notification.

In the illustrated embodiment of a screen clean notification API(21010), the screen clean notification API may be defined as“org.atsc.notify”. The screen clean notification API may include a JSONobject 21010.

The JSON object 21010 may further include msgType as well as validFrom,validUntil, and/or clean of the aforementioned screen clean request API.

The validFrom, validUntil, and clean elements may have the same meaningas in the aforementioned screen clean request API. The msgType mayindicate a type of a message to be transmitted through a correspondingJSON object. Here, the msgType may indicate ScreenClean.

In some embodiments, when a JSON object is transmitted to an applicationaccording to a screen clean notification API, the application may notrespond thereto. Accordingly, ‘id’ information may be omitted from theJSON object.

In the illustrated application example of the screen clean notificationAPI (21020), the broadcast service processing apparatus may issue thescreen clean notification API to an application. The screen cleannotification API may be defined as “org.atsc.notify”. The JSON objectmay include the aforementioned clean flag. It may be seen that the flagmay be valid to “2017-01-01T23:59:59.590Z” from“2017-01-01T23:54:59.590Z”.

The aforementioned screen clean notification APIs according toembodiments of the present invention may be combined. In a broadcastservice processing apparatus according to embodiments of the presentinvention, a screen clean notification API may be the aforementionedscreen clean notification API according to embodiments of the presentinvention.

FIG. 22 is a diagram showing a display override request API according toan embodiment of the present invention.

The display override request API according to the present invention maybe an API issued to a broadcast service processing apparatus by anapplication and may be an API for transmitting information items relatedto change in an image by OSN in the form of a flag. Information itemssuch as resourceBlocking and displayOverride may be transmitted by theAPI.

The application may intend to know whether the broadcast serviceprocessing apparatus receives ‘display override’ signaling through awatermark or the like. Here, the display override may indicate whethermodification is not required to be performed on video/audiopresentation. Alternatively, the display override may signal whether anapplication needs to block access to a presentation resource (resourceblocking). In some embodiments, the application may intend to knowwhether the broadcast service processing apparatus receives OSNinformation, as described above.

The display override information and/or the OSN information may be usedby an application to effectively use a broadcast service processingapparatus and/or a network resource. For example, the application maynot make a request for resources that are not capable of beingreproduced to a user, to a broadband server.

The information may be used to preserve accurate reproduction of userexperience. For example, the application may accurately reportviewability of dynamically inserted advertisement as requirement ofadvertisement viewability standard.

The information may be used to satisfy requirement of a display overridestate. For example, the application may block modification ofaudio/video when the broadcast service processing apparatus does notperform resource blocking.

In the illustrated embodiment of a display override request API, thedisplay override request API may be defined as“org.atsc.query.displayOverride”. A parameter of the API may be omitted.

In addition, the broadcast service processing apparatus may transmit aresponse to the display override request API to the application (22010).A response thereto may include a JSON object 22010.

The JSON object may include resourceBlocking and/or displayOverride.

The resourceBlocking may indicate whether the broadcast serviceprocessing apparatus blocks the application to reproduce video/audioaccording to an active display override state. The resourceBlocking maybe a required element and may be Boolean format. In some embodiments,resourceBlocking information may be basically in a false state.

The displayOverride may indicate whether a current display overridestate is valid, such as a display override message of a video watermarkor display override indication of an audio watermark. ThedisplayOverride may be a required element and may be Boolean format. ThedisplayOverride may be determined by an OSN fragment. In someembodiments, displayOverride information may be basically in a falsestate.

In some embodiments, when there is no key/value pair, this may indicatethat corresponding values are a false value.

In the illustrated application example of a display override requestAPI, an application may issue the display override request API to abroadcast service processing apparatus (22020). The display overriderequest API may be defined as “org.atsc.query.resourceBlocking”.

In response to the display override request API, the broadcast serviceprocessing apparatus may also return a JSON object to the application(22030). In the JSON object, resourceBlocking and displayOverride mayhave a true value. In this case, a display override condition iscurrently indicated by an audio watermark and the broadcast serviceprocessing apparatus blocks the application to reproduce video/audio.

In response to the display override request API, the broadcast serviceprocessing apparatus may also return the JSON object to the application(2204). In the JSON object, resourceBlocking and displayOverride mayhave false and true values, respectively. In this case, a displayoverride state is currently changed by the OSN fragment.

The aforementioned display override request APIs according toembodiments of the present invention may be combined. In a broadcastservice processing apparatus according to embodiments of the presentinvention, a display override request API may be the aforementioneddisplay override request API according to embodiments of the presentinvention.

FIG. 23 is a diagram showing a method of acquiring a WebSocket severaddress by an application according to an embodiment of the presentinvention.

The method of acquiring a WebSocket sever address by an applicationaccording to the present invention may be a method for accessing aWebSocket sever of the broadcast service processing apparatus. Theaforementioned broadcast service processing apparatus may furtherinclude a WebSocket sever. The application may use various methods toaccess the WebSocket sever.

In a next-generation broadcast system, a communication protocol betweena primary device (PD) and a companion device (CD) may be defined. Here,the PD may correspond to the aforementioned broadcast service processingapparatus. On a web browser of the PD, a PD application may be executed.Here, the web browser may be driven by the aforementioned processor ofthe broadcast service processing apparatus. The PD application mayinteract with a CD application through a WebSocket server of the PD.Methods of acquiring a URL of the WebSocket server may be defined toaccess the WebSocket server by the PD application.

The method of acquiring a WebSocket sever address by an application,i.e., methods of acquiring a URL of the WebSocket sever for access tothe WebSocket sever by the PD application will now be described.

In some embodiments, the PD application may pre-acquire a WebSocket URLwhen the application is launched. Here, the application may be launchedthrough the following WebSocket communication.

http://localhost/xbc.org/x.y.z/home.html?wsURL=wss://localhost:8000

In the illustrated table of a WebSocket server function and URLs,WSPath/astsCD may be added as in a last row. Thereby, the PD applicationand/or CD and a URL of the WebSocket server for the CD application maybe acquired as follows.

wss://localhost:8000/atscCD

In some embodiments, a query component for a WebSocket URL when anapplication is executed may be defined. cdwsURL for a CD WebSocketserver may be defined and the query component may be defined as follows.

query=“cdwsURL=” ws-url

Here, when an entry page URL ishttp://localhost/xbc.org/x.y.z/home.html, the application may beexecuted as follows.

http://localhost/xbc.org/x.y.z/home.html?wsURL=wss://localhost:8000?cdwsURL=wss://localhost:8800

Here, the URL of the CD WebSocket server may be checked as follows.

wss://localhost:8800

In some embodiments, an existing defined JSON objet API may be changedand used in the form of JSON RPC. In this case, the CD WebSocket servermay be an integrated Command and Control Websocket Server.

In some embodiments, getApp2AppLocalBaseURL( ) that is conventionallydefined in HbbTV may be used. The getApp2AppLocalBaseURL( ) may becommunication for returning a base URL of an application to anapplication communication service local end point. Communication betweenthe HbbTV application and a remote client may be performed through theendpoint. A URL acquired via this method may be ended with slash (/). AURL of the WebSocket server may be acquired usinggetApp2AppLocalBaseURL( ).

The aforementioned methods of acquiring a WebSocket server addressaccording to embodiments of the present invention may be combined. In abroadcast service processing apparatus according embodiments of thepresent invention, a method of acquiring a WebSocket server address byan application may be the aforementioned method of acquiring theWebSocket server address by the application according to theaforementioned of the present invention.

FIG. 24 is a diagram showing a method of processing a broadcast serviceto be performed by a broadcast service processing apparatus according toan embodiment of the present invention.

The method of processing a broadcast service in an apparatus includes,receiving a broadcast signal, receiving, from an application running onthe apparatus, a request based on a first Application ProgrammingInterface (API), generating a first JavaScript Object Notation (JSON)object by including the URL for the requested OSN and delivering, to theapplication, the first JSON object in response to the first API.

The tuner can receive a broadcast signal including service data for thebroadcast service and signaling information for signaling the broadcastservice. Here, the signaling information includes On Screen messageNotification (OSN) which indicates a preference of a broadcaster for theapparatus to avoid obscuring video images of the broadcast service. Thesignaling information can be delivered to the apparatus in various ways.Here, the apparatus may correspond to the apparatus for the processingthe broadcast service.

The processor can communicate with an application running on theapparatus. The processor can receive, from the application, a requestbased on a first Application Programming Interface (API). The first APImay correspond to ‘URL request API’ described above. The first APIincludes information for indicating that the request is for a UniformResource Locator (URL) referencing the most recent OSN.

The processor can generate a first JavaScript Object Notation (JSON)object by including the URL for the requested OSN. Then the processorcan deliver, to the application, the first JSON object in response tothe first API.

In the method of processing a broadcast service according to otherembodiment of the present invention, in step of the generating the firstJSON object, the processor may add adding time information to the firstJSON object. Here, the time information is for indicating when therequested OSN is received.

In the method of processing a broadcast service according to anotherembodiment of the present invention, the processor may receive asubscription from the application based on a second API. The second APImay correspond to ‘signaling change subscribe API’. The second API isfor the application to be notified when changes in an OSN occur.

In the method of processing a broadcast service according to anotherembodiment of the present invention, the second API issued by theapplication includes a second JSON object, and the second JSON objectincludes information for requesting the apparatus to notify theapplication when a new or updated OSN is received.

In the method of processing a broadcast service according to anotherembodiment of the present invention, the processor may deliver anotification to the subscribed application by issuing a third API. Thethird API may correspond to ‘signaling change notification API’. Thethird API is for delivering the notification indicating a presence ofchanges in an OSN.

In the method of processing a broadcast service according to anotherembodiment of the present invention, the notification based on the thirdAPI includes a third JSON object, and the third JSON object includes anURL for referencing a new or updated OSN and time information forindicating when the new or updated OSN is received.

In the method of processing a broadcast service according to anotherembodiment of the present invention, the application communicates withthe apparatus via a WebSocket protocol.

The methods of processing a broadcast service according to embodimentsof the present invention may be combined.

Modules or units may correspond to processors that execute continuousprocesses stored in a memory (or a storage unit). The respective stepsdescribed in the above-described embodiments may be performed byhardware/processors. The respective modules/blocks/units described inthe above embodiments may operate as hardware/processors. In addition,the methods proposed in the present invention may be executed as codes.These codes may be written in a processor-readable storage medium, andthus may be read by a processor provided by an apparatus.

Even though the respective drawings have been separately described forconvenience of description, embodiments described in the respectivedrawings may be merged into a new embodiment. In addition, designing ofa computer-readable recording medium in which a program for executingthe above-described embodiments according to necessity of a personskilled in the art is within the scope of the present invention.

Referring to the apparatuses and methods according to the presentinvention, configurations and methods of the embodiments are notrestrictively applicable, and all or some of the above-describedembodiments may be selectively combined and configured such that theembodiments can be variously changed

Meanwhile, the methods proposed in the present invention may beimplemented as processor-readable code stored in a processor-readablerecording medium included in a network device. The processor-readablerecording medium includes all types of recording devices in whichprocessor-readable data is stored. Examples of the processor-readablerecording medium include a ROM, a RAM, a CD-ROM, a magnetic tape, afloppy disk, an optical data storage device, etc. In addition, theexamples include a carrier-wave type implementation such as atransmission over the Internet. Furthermore, as the processor-readablerecording medium is distributed to a computer system connected via anetwork, processor-readable code can be saved and executed in adistributed manner.

Further, even though preferred embodiments of the present invention havebeen illustrated and described, the present invention is not restrictedto a certain embodiment described above, and various modifications andvariations can be made by those skilled in the art without departingfrom the subject matter of the present invention as defined by theclaims. Furthermore, these modified embodiments should not be understoodseparately from the spirit or scope of the present invention.

Both apparatus and method inventions are mentioned in this specificationand descriptions of both the apparatus and method inventions may becomplementarily applicable to each other.

It should be understood by those skilled in the art that various changesand modifications can be made in the present invention within the spiritor scope of the present invention. Therefore, the present invention isintended to include changes and modifications of the present inventionwithin the scope of accompanying claims and equivalents thereof.

Both apparatus and method inventions are mentioned in this specificationand descriptions of both the apparatus and method inventions may becomplementarily applicable to each other.

MODE FOR INVENTION

Various embodiments have been described in best modes.

INDUSTRIAL APPLICABILITY

The present invention is used in a series of broadcast signal provisionfields.

It is clear to those skilled in the art that various changes andmodifications can be made in the present invention within the spirit orscope of the present invention. Therefore, the present invention isintended to include changes and modifications of the present inventionwithin the scope of accompanying claims and equivalents thereof.

What is claimed is:
 1. A method of processing a broadcast service in anapparatus, the method comprising: receiving a broadcast signal includingservice data for the broadcast service and signaling information forsignaling the broadcast service, wherein the signaling informationincludes On Screen message Notification (OSN) which notifies to areceiver a preference of a broadcaster for the receiver to avoidobscuring a part of video images, and wherein the OSN includes durationinformation for identifying a duration of KeepScreenClear informationrelated to keep screen clear status corresponding to on-screen text orvisual information, flag information for identifying a status of theKeepScreenClear information and version information for identifying aversion of the KeepScreenClear information; receiving, from anapplication running on the apparatus, a request based on a firstApplication Programming Interface (API), wherein the first API includesinformation for identifying that the request is for an Uniform ResourceLocator (URL) referencing the most recent OSN; generating a firstJavaScript Object Notation (JSON) object by including the URL for therequested OSN; and delivering, to the application, the first JSON objectin response to the first API.
 2. The method of claim 1, wherein thegenerating the first JSON object further comprising comprises: addingtime information to the first JSON object, the time information foridentifying when the requested OSN is received.
 3. The method of claim1, further comprising: receiving a subscription from the applicationbased on a second API, wherein the second API is for the application tobe notified when changes in an OSN occur.
 4. The method of claim 3,wherein the second API issued by the application includes a second JSONobject and wherein the second JSON object includes information forrequesting the apparatus to notify the application when a new or updatedOSN is received.
 5. The method of claim 3, further comprising:delivering a notification to the subscribed application by issuing athird API, wherein the third API is for delivering the notification foridentifying a presence of changes in an OSN.
 6. The method of claim 5,wherein the notification based on the third API includes a third JSONobject, and wherein the third JSON object includes an URL forreferencing a new or updated OSN and time information for identifyingwhen the new or updated OSN is received.
 7. The method of claim 1,wherein the application communicates with the apparatus via an WebSocketprotocol.
 8. An apparatus for processing a broadcast service, theapparatus comprising: a tuner configured to receive a broadcast signalincluding service data for the broadcast service and signalinginformation for signaling the broadcast service, wherein the signalinginformation includes On Screen message Notification (OSN) which notifiesto a receiver a preference of a broadcaster for the receiver to avoidobscuring a part of video images, and wherein the OSN includes durationinformation for identifying a duration of KeepScreenClear informationrelated to keep screen clear status corresponding to on-screen text orvisual information, flag information for identifying a status of theKeepScreenClear information and version information for identifying aversion of the KeepScreenClear information; and a processor operativelycoupled to the tuner and configured to: receive, from an applicationrunning on the apparatus, a request based on a first ApplicationProgramming Interface (API), wherein the first API includes informationfor identifying that the request is for an Uniform Resource Locator(URL) referencing the most recent OSN, generate a first JavaScriptObject Notation (JSON) object by including the URL for the requestedOSN, and deliver, to the application, the first JSON object in responseto the first API.
 9. The apparatus of claim 8, wherein, to generate thefirst JSON object, the processor is further configured to: add timeinformation to the first JSON object, the time information foridentifying when the requested OSN is received.
 10. The apparatus ofclaim 8, wherein the processor is further configured to: receive asubscription from the application based on a second API, wherein thesecond API is for the application to be notified when changes in an OSNoccur.
 11. The apparatus of claim 10, wherein the second API issued bythe application includes a second JSON object, and wherein the secondJSON object includes information for requesting the apparatus to notifythe application when a new or updated OSN is received.
 12. The apparatusof claim 10, wherein the processor is further configured to: deliver anotification to the subscribed application by issuing a third API,wherein the third API is for delivering the notification for identifyinga presence of changes in an OSN.
 13. The apparatus of claim 12, whereinthe notification based on the third API includes a third JSON object,and wherein the third JSON object includes an URL for referencing a newor updated OSN and time information for identifying when the new orupdated OSN is received.
 14. The apparatus of claim 8, wherein theapplication communicates with the apparatus via an WebSocket protocol.